Wireless lighting control system

ABSTRACT

A lighting device includes a AC/DC or DC/DC power converter, a controller/processor electrically connected to the AC/DC or DC/DC power converter, a light emitting diode (LED) current control circuit communicably coupled to the controller/processor and electrically connected to the AC/DC or DC/DC power converter, and one or more LEDs electrically connected to the LED current control circuit.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and is: (1) a non-provisional patentapplication of U.S. Provisional Patent Application Ser. No. 61/724,651,filed on Nov. 9, 2012, and entitled “Wireless Lighting Control System”;and (2) a continuation-in-part application of U.S. patent applicationSer. No. 13/836,280, filed on Mar. 15, 2013, and entitled “WirelessLighting Control System”, which (a) is a continuation application ofU.S. patent application Ser. No. 13/417,322, filed Mar. 11, 2012, andentitled “Wireless Lighting Control System”, which is a non-provisionalpatent application of U.S. Provisional Application Ser. No. 61/464,917,filed Mar. 11, 2011, and entitled “Specialty Lighting and ControlTherefor”, and (b) claimed priority to PCT Patent Application SerialNumber PCT/US2012/037369, filed May 10, 2012, and entitled “WirelessLighting Control System.” The foregoing applications are herebyincorporated by reference in their entirety.

This application is also related to: (1) U.S. patent application Ser.No. 13/837,232, filed on Mar. 15, 2013, and entitled “Wireless LightingControl System”; (2) U.S. patent application Ser. No. 13/838,648, filedon Mar. 15, 2013, and entitled “Wireless Lighting Control System”; and(3) U.S. patent application Ser. No. 13/839,738, filed on Mar. 15, 2013,and entitled “Wireless Lighting Control System”. The foregoingapplications are hereby incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates generally to the field of lighting and,more particularly, to a specialty lighting device and control processfor individual or simultaneous adjustment, automation, and programmingof an individual or network of such light bulbs through a wirelessinterface.

BACKGROUND OF THE INVENTION

In response to government mandates, new lighting technologies, such aslight emitting diodes(LEDs) or compact fluorescent lamps(CFLs), areentering the market at a rapid pace. However, these bulbs havelimitations that make them unattractive to some users. CFLs have dimminglimitations, take a few minutes to warm-up, and have problems with theircolor output. Additionally, CFLs contain mercury, a toxic and regulatedsubstance, which creates issues with disposal. LEDs are currently veryexpensive in comparison and the high cost has dissuaded many consumersfrom their purchase.

Additionally, current lighting control and automation solutions arelimited in their use in rental or temporary situations where the systemshigh price, required installation, and expertise in set-up are aproblem. Further, as mobile computing systems continue to evolve, manypeople have shown a preference towards using their mobile device as aconverged platform to control and execute multiple other tasks. Althougha multitude of types of light types and luminaries have been created tohelp create a mood or environment, most if not all of these solutionsonly exist in a single state and are limited by the network power line.This has driven the complexity in bulb wattage, fixtures, wall-switches,shades, and other attempts at creating the ability to augment theatmosphere created by a light. If you want to dim one bulb, currentsolutions generally only allow for a wall-switch dimmer. The ability toaddress and adjust a single light individually or network of lightssimultaneously is currently not possible without extensive installation.

SUMMARY OF THE INVENTION

The present invention provides an easily installed and transferablelighting and home automation solution because special or customizedinstallation is not required. The present invention presents a solutionto controlling and programming lighting devices such that the color andbrightness of any individual light or a group of lights can be manuallyor automatically controlled using a wireless interface. A user has theflexibility to personalize the color, atmosphere, and mood of a room tobetter fit ones preference, time of day, or occasion at hand.

Additionally, since the present invention requires no installation, thesolution is fully portable and can be removed and reused in otherlocations throughout the long life of the device. Essentially, thepresent invention is an automation and custom lighting solution that cantravel with you.

Automation and dimming of the lighting devices save more energy than isconsumed by the additional components of the lighting device. Moreover,using on/off signals having specified cycle times to produce a blendedlight reduce the current requirements of the lighting device. Lastly,holistically speaking the iLumi solution itself will help to drive theadoption of LED bulbs, providing an LED solution whose value outweighsits price.

More specifically, the present invention provides a lighting device thatincludes a AC/DC or DC/DC power converter, a controller/processorelectrically connected to the AC/DC or DC/DC power converter, a lightemitting diode (LED) current control circuit communicably coupled to thecontroller/processor and electrically connected to the AC/DC or DC/DCpower converter, and one or more LEDs electrically connected to the LEDcurrent control circuit.

Moreover, the present invention provides a lighting device that includesa flexible strip, an electrical connector affixed to the flexible stripand two or more LEDs affixed to the flexible strip and electricallyconnected to the electrical connector. In addition, an AC/DC or DC/DCpower converter, a controller/processor and a LED current controlcircuit are remotely located with respect to the flexible strip andelectrically connected to the electrical connector via a wire, a cableor a connecting strip.

Furthermore, the present invention provides a lighting device thatincludes a housing, an AC/DC or DC/DC power converter, acontroller/processor electrically connected to the AC/DC or DC/DC powerconverter, a light emitting diode (LED) current control circuitcommunicably coupled to the controller/processor and electricallyconnected to the AC/DC or DC/DC power converter, and one or more LEDselectrically connected to the LED current control circuit. The AC/DC orDC/DC power converter, the controller/processor and the LED currentcontrol circuit are disposed within the housing, and the one or moreLEDs are proximate to or within an aperture of the housing.

In addition, the present invention provides a lighting system thatincludes two or more lighting devices. Each lighting device includes anAC/DC or DC/DC power converter, a controller/processor electricallyconnected to the AC/DC or DC/DC power converter, a light emitting diode(LED) current control circuit communicably coupled to thecontroller/processor and electrically connected to the AC/DC or DC/DCpower converter, and one or more LEDs electrically connected to the LEDcurrent control circuit. The controller/processors of the two or morelighting devices communicate with one another using the wirelesstransceivers and antennas of the two or more lighting devices.

The present invention also provides method for controlling one or morelighting devices by providing the one or more lighting devices, whereineach lighting device includes an AC/DC or DC/DC power converter, acontroller/processor electrically connected to the AC/DC or DC/DC powerconverter, a light emitting diode (LED) current control circuitcommunicably coupled to the controller/processor and electricallyconnected to the AC/DC or DC/DC power converter, and one or more LEDselectrically connected to the LED current control circuit.

These and other objects, advantages and features of this invention willbe apparent from the following description taken with reference to theaccompanying drawing, wherein is shown a preferred embodiment of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings, in which:

FIG. 1 is a block diagram of a lighting device in accordance with oneembodiment of the present invention;

FIG. 2 is a circuit diagram of a single LED arm with single LED inaccordance with one embodiment of the present invention;

FIG. 3 is a circuit diagram of a solely LED Drivers scheme in accordancewith one embodiment of the present invention;

FIG. 4 is a timing diagram for the solely LED drivers scheme of FIG. 3;

FIG. 5 is a circuit diagram of switches and LED driver scheme inaccordance with one embodiment of the present invention;

FIG. 6 is a timing diagram for the switches and LED driver scheme ofFIG. 5;

FIG. 7 is a circuit diagram of a multiplexer and a LED driver scheme inaccordance with one embodiment of the present invention;

FIG. 8 is a circuit diagram of current limiting circuit scheme inaccordance with one embodiment of the present invention;

FIG. 9 is a diagram of a mechanical model for a Smartstrip Light inaccordance with one embodiment of the present invention;

FIG. 10 is a block diagram of a Smartstrip light in accordance with oneembodiment of the present invention;

FIG. 11 is a circuit diagram of LED groups on a LED strip in accordancewith one embodiment of the present invention;

FIGS. 12A-1 and 12A-2 are block diagrams of a front view and a rearview, respectively, of a LED strip in accordance with one embodiment ofthe present invention;

FIGS. 12B-1 and 12B-2 are block diagrams of a front view and a rearview, respectively, of an extendible LED strip in accordance with oneembodiment of the present invention;

FIG. 13 is a block diagram of the mechanical and electrical connectionsfor the Smartstrip in accordance with one embodiment of the presentinvention;

FIG. 14 is a block diagram of an extendible LED strip in accordance withone embodiment of the present invention;

FIG. 15 is a block diagram of a LED strip extension through parallelconnection in accordance with one embodiment of the present invention;

FIG. 16 is a block diagram of a LED strip direct connection inaccordance with one embodiment of the present invention;

FIG. 17 is a block diagram of a LED strip connection through wire inaccordance with one embodiment of the present invention;

FIG. 18 is a perspective view of an Intelligent Illuminating Bulb inaccordance with one embodiment of the present invention;

FIG. 19 is an exploded perspective view of an Intelligent IlluminatingBulb in accordance with one embodiment of the present invention;

FIG. 20 is a diagram of a LED board in accordance with one embodiment ofthe present invention;

FIG. 21 is a flow chart of a status request/update process for awireless device or auxiliary device to Intelligent Illuminating Devicein accordance with one embodiment of the present invention;

FIG. 22 is a flow chart of a status update process for IntelligentIlluminating Device to Intelligent Illuminating Device in accordancewith one embodiment of the present invention;

FIG. 23 is a flow chart of a communication process from a device toIntelligent Illuminating Device in accordance with one embodiment of thepresent invention;

FIG. 24 is a flow chart of a communication process from a device tomultiple Intelligent Illuminating Devices in accordance with oneembodiment of the present invention;

FIG. 25 is a block diagram of accessing an Intelligent IlluminatingDevice network through various devices in accordance with one embodimentof the present invention;

FIG. 26 is a flow chart of a wireless device update date/time process inIntelligent Illuminating Device in accordance with one embodiment of thepresent invention;

FIG. 27 is a flow chart of an Intelligent Illuminating Device updatedate/time in Intelligent Illuminating Device in accordance with oneembodiment of the present invention;

FIG. 28 is a flow chart of basic control areas in accordance with oneembodiment of the present invention;

FIG. 29 is a flow chart of a programming process in accordance with oneembodiment of the present invention;

FIG. 30 is a flow chart of a process for creating a scene in accordancewith one embodiment of the present invention;

FIG. 31 is a flow chart of a process for executing a scene command inaccordance with one embodiment of the present invention;

FIG. 32 is a flow chart of a process for creating a new group or addingto a new group in accordance with one embodiment of the presentinvention;

FIG. 33 is a flow chart of a process for sending a group command inaccordance with one embodiment of the present invention;

FIG. 34 is a flow chart of a process for creating or adjusting a lightdefault in accordance with one embodiment of the present invention;

FIG. 35 is a flow chart of a process for creating or adjust a groupdefault in accordance with one embodiment of the present invention;

FIG. 36 is a flow chart of a power restoration process in accordancewith one embodiment of the present invention;

FIG. 37 is a flow chart of a process for executing a default commandthrough an on/off toggle in accordance with one embodiment of thepresent invention;

FIG. 38A-F are diagrams of various screens on device application inaccordance with one embodiment of the present invention;

FIG. 39 is a flow chart of a quick set-up process for connected lightsin accordance with one embodiment of the present invention;

FIG. 40 is a flow chart of a quick group process through powerrestoration in accordance with one embodiment of the present invention;

FIG. 41 is a flow chart of a profile authentication process inaccordance with one embodiment of the present invention;

FIG. 42 is a flow chart of a process for saving settings under a profilein accordance with one embodiment of the present invention;

FIG. 43 is a block diagram of a device to device profile sharing processin accordance with one embodiment of the present invention;

FIG. 44 is a flow chart of a process for adding an authenticated profiledirectly through the Intelligent Illuminating Device in accordance withone embodiment of the present invention;

FIG. 45 is a flow chart of a hard reset process in accordance with oneembodiment of the present invention;

FIG. 46 is a flow chart of a soft reset through application inaccordance with one embodiment of the present invention;

FIG. 47 is a flow chart of a process for adding a new IntelligentIlluminating Device into an existing Intelligent Illuminating Devicenetwork in accordance with one embodiment of the present invention;

FIG. 48 is a block diagram of another embodiment of II Device systemwith a wireless energy receiver and transmitter in accordance with oneembodiment of the present invention;

FIG. 49 is a block diagram of a color coding identification process inaccordance with one embodiment of the present invention;

FIG. 50 is a block diagram of sorting based on signal strength inaccordance with one embodiment of the present invention;

FIG. 51 is a block diagram of sorting based on status in accordance withone embodiment of the present invention;

FIG. 52 is a block diagram of sorting based on available IntelligentIlluminating Devices in accordance with one embodiment of the presentinvention;

FIG. 53 is a flow chart of an automation programming process inaccordance with one embodiment of the present invention; and

FIG. 54 is a flow chart of a music sync process in accordance with oneembodiment of the present invention;

FIG. 55 is a block diagram of showing a potential placement of thephotosensor and reset switch on the light mixing cover/diffuser inaccordance with one embodiment of the present invention;

FIG. 56 is a block diagram of an Intelligent Illuminating Device networkin accordance with one embodiment of the present invention;

FIG. 57 is a block diagram of an Intelligent Illuminating Can inaccordance with one embodiment of the present invention;

FIG. 58 is a block diagram of a LED driver scheme in accordance with oneembodiment of the present invention;

FIG. 59 is a flow chart of a controller/processor and LED driver schemein accordance with one embodiment of the present invention;

FIGS. 60A-60B and 61 are timing diagrams in accordance with variousembodiments of the present invention;

FIG. 62 is a block diagram of a lighting system in accordance with oneembodiment of the present invention;

FIG. 63 is a block diagram of a sensor device capable of communicatingwith and controlling the IID(s) to control IID in accordance with oneembodiment of the present invention;

FIG. 64 is a block diagram of a remote controlling device and a sensorcapable of communicating with and controlling the IID(s) to control IIDin accordance with another embodiment of the present invention;

FIG. 65 is a flow chart of functions to implement different applicationsor features in accordance with one embodiment of the present invention;

FIG. 66 is a block diagram illustrating how the signal strength can varybased on location and proximity in accordance with one embodiment of thepresent invention;

FIG. 67 shows examples of an application interface for controlling oneor more lights in accordance with various embodiments of the presentinvention;

FIG. 68 shows examples of an application interface for color wheelcontrol in accordance with various embodiments of the present invention;

FIG. 69 is a flow chart of scheduling programs for operating a lightingdevice in accordance with one embodiment of the present invention;

FIG. 70 is a flow chart of selecting a lighting sequence of a lightingdevice in accordance with one embodiment of the present invention;

FIG. 71 is a flow chart of storing various parameters for a lightingdevice in accordance with the present invention;

FIG. 72 is a flow chart illustrating using voice commands to control alighting device in accordance with the present invention;

FIG. 73 is a flow chart illustrating setting up a network of lightingdevices in accordance with one embodiment of the present invention;

FIGS. 74 and 75 are a block diagram and flow chart for broadcastingcommands in accordance with one embodiment of the present invention;

FIG. 76 illustrates an example of forming lighting devices from variousparts in accordance with one embodiment of the present invention;

FIG. 77 is a flow chart illustrating a program for designing a lightingdevice in accordance with one embodiment of the present invention;

FIG. 78 is a block diagram showing a lighting device for geographical orspace travel in accordance with one embodiment of the present invention;

FIG. 79 is a flow chart illustrating how a user might want to program alighting device to produce light as a function of at least one variablein accordance with one embodiment of the present invention;

FIG. 80 is a flow chart illustrating how a user can define the colortemperature of the light output as a function of time in accordance withone embodiment of the present invention;

FIG. 81 is a flow chart illustrating how a user assigns the priority forvarious programs through the user interface software running on thewireless device for controlling a lighting device in accordance with oneembodiment of the present invention;

FIG. 82 is a block diagram illustrating how a lighting device can beused with fluorescent objects in accordance with one embodiment of thepresent invention;

FIG. 83 is a flow chart illustrating how a lighting device can be usedwith fluorescent objects or laser diodes in accordance with oneembodiment of the present invention;

FIG. 84 is a flow chart of a scheduling program for a lighting device inaccordance with one embodiment of the present invention;

FIG. 85 is a flow chart of an eco mode for a lighting device inaccordance with one embodiment of the present invention;

FIG. 86 is a flow chart of monitoring program for a lighting device inaccordance with one embodiment of the present invention;

FIG. 87 is a flow chart of a data program for a lighting device inaccordance with one embodiment of the present invention;

FIG. 88 is a flow chart of recording program for a lighting device inaccordance with one embodiment of the present invention;

FIG. 89 is a flow chart of image reflection program for a lightingdevice in accordance with one embodiment of the present invention;

FIG. 90 is a flow chart of quick scene creation program for a lightingdevice in accordance with one embodiment of the present invention; and

FIG. 91 is a flow chart of location services and interaction program fora lighting device in accordance with one embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

While the making and using of various embodiments of the presentinvention are discussed in detail below, it should be appreciated thatthe present invention provides many applicable inventive concepts thatcan be embodied in a wide variety of specific contexts. The specificembodiments discussed herein are merely illustrative of specific ways tomake and use the invention and do not delimit the scope of theinvention.

The present invention provides an easily installed and transferablelighting and home automation solution because special or customizedinstallation is not required. The present invention presents a solutionto controlling, programming, and automating lighting devices, such thatthe color and brightness of any individual light or a group of lightscan be manually or automatically controlled using a wireless interface.A user has the flexibility to personalize the color, atmosphere, andmood of a room to better fit ones preference, time of day, or occasionat hand. Additionally, since the present invention requires noinstallation, the solution is fully portable and can be removed andreused in other locations throughout the long life of the lightingdevice. Automation and dimming of the lighting devices save more energythan is consumed by the additional components of the lighting device.Moreover, using on/off signals having specified cycle times to produce ablended light reduce the current requirements of the lighting device.

The present invention, a wireless lighting control system, consists ofmethods, apparatuses, and associated software (device application) forcontrolling, programming, and automating one and/or multiple‘Intelligent Illuminating Devices’ (II Device) utilizing a wirelesscommunication protocol executed between one or many wireless devices andone or many II Devices (II Device network). The methods and apparatusespresented here would allow one to adjust and control a single or networkof II Devices with high flexibility, user control, and intuitive userinteraction, with minimal installation or complexity.

For the purposes of discussing this invention the following terms willbe used to describe the primary aspects of the invention. An II Deviceis a single wirelessly enabled lighting apparatus. A wireless device isa computing device such as a smartphone, computer, tablet, smartTV,remote, etc. A device application is a user facing software applicationrun on the wireless device. A mesh network is a wireless communicationprotocol used to connect one or many II Devices and/or one or manywireless devices.

The light is a combination of a light generator, a light detector, acommunicator, a power source, and a computer processor. In oneembodiment these components are contained within one form factor similarto a standard light bulb. In other embodiments these elements will beseparate from the other elements. For example, the light generator canbe separate from the remaining components. In other embodiments, not allof the components are required. For example, one embodiment may consistsolely of the lighting generator, communicator and computer processor.In other embodiments, an outside light-sensing component may be used.For example, an outside light-sensing component might be disparatelyconnected to the remaining components.

An II Device in the context of this invention is a lighting apparatuscontaining additional electronic circuits and components. In oneembodiment, the II Device will produce some measure or effect ofluminosity dependent on commands sent wirelessly through a wirelessdevice and associated device application. The II Device can receivewireless communications, take immediate action (in terms of a lightingoutput) based on the wireless communication, execute a sequence ofactions, and store one or more commands to be executed at a specifiedtime in the future or upon a specified condition being met. In addition,one embodiment of the II Device can intelligently relay/transmitwireless communication commands received from a device application (orII Device) to other II Devices within proximity. Similarly, oneembodiment of the II Device would confirm receipt of the command througha wireless communication back to the wireless device and deviceapplication, possibly relaying the confirmation back through other IIDevices. The communication means for to execute these processes can beseen in the mesh network section.

Now referring to FIG. 1, a block diagram of a lighting device inaccordance with one embodiment of the present invention is shown. Thelighting device (II Device) 140 might take numerous forms or embodimentsin design, but certain components are common to the various designswhile others will be used as is necessary for a specific embodiment.These components may or may not be part of II Device 140 and might bearranged in different fashion and with slight alteration to createdifferent intelligent illuminating embodiments. For example, the IIDevice 140 includes a DC/DC power converter 104, a controller/processor106 electrically connected to the DC/DC power converter 104, a lightemitting diode (LED) current control circuit 120 communicably coupled tothe controller/processor 106 and electrically connected to the DC/DCpower converter 104, and two or more LEDs 122 electrically connected tothe LED current control circuit 120. The LED current control circuit 120can be a PWM driver, switching or multiplexer circuit, or light emittingdiodes (LEDs) driver(s) circuit. The two or more LEDs 122 will includeat least a first color LED 122 a and a second color LED 122 b. Moreover,at least one of the LEDs 122 may include a series of LEDs, a group ofLEDs, an array of LEDs, two or more series-connected LEDs, two or moreparallel-connected LEDs or a combination thereof. Typically, the firstcolor LED 122 a and the second color LED 122 b will be selected from ared LED, a green LED, a blue LED, a red LED, a white LED, a tri-colorLED and a four-color LED.

As will be explained in more detail below, a method for controlling oneor more lighting devices 140 includes the steps of providing the one ormore lighting devices 140, sending one or more control signals from thecontroller/processor 106 to the LED current control circuit 120corresponding to a blended light having a specified color, and sendingan on/off signal having a cycle time from the LED current controlcircuit 120 to each LED 122 in response to the one or more controlsignals such that the two or more LEDs 122 produce the blended lighthaving the specified color based on how long each LED 122 is turned ONand/or OFF during the cycle time. The LED current control circuit 120provides an on/off signal having a cycle time to each LED 122 inresponse to one or more control signals received from thecontroller/processor 106 such that the two or more LEDs 122 produce ablended light having a specified color based on how long each LED isturned ON and/or OFF during the cycle time. These on/off signals withspecified cycle times to produce a blended light can be used to reducethe current requirements of the II Device 140.

Other embodiments will include additional components. For example, theadditional components may include: a power supply connector/fastener100; an AC/DC power converter 102 electrically connected to the powersupply connector/fastener 100 and the DC/DC power converter 104; a realtime clock (RTC) circuit 110 communicably coupled to thecontroller/processor 106; a memory 108 communicably coupled to thecontroller/processor 106; a wireless transceiver circuit 112communicably coupled to the controller/processor 106; an antenna 114communicably coupled to the wireless transceiver circuit 112; a hardreset circuit 116 communicably coupled to the controller/processor 106;an ambient light sensor circuit 118 communicably coupled to thecontroller/processor 106; a heat sink 124; a reflector 126 disposedbehind or around the two or more LEDs 122; and/or a diffuser or lens 128disposed above the two or more LEDs 122.

The components of the II Device 140 can be modularized to provide easyenhancement, customization, modification and repair of the II Device140. For example, a main circuit board 134 may include the DC/DC powerconverter 104, the controller/processor 106, the LED current controlcircuit 120, the memory 108, the real time clock circuit 110, and thewireless transceiver circuit 112 and antenna 114. A sensor board 130 mayinclude the hard reset circuit 116 and the ambient light sensor circuit118. A LED board 136 may include the two or more LEDs 122 and additionalLED related circuitry (e.g., LED arms).

The connector 100 performs at least one of two functions. One, it canphysically connect the II Device 140 to a surface and two, it canprovide access to a power source. The connector 100 could fasten to astandard surface, light socket, or electrical socket, or combination ofthe like. Similarly, the connector 100 could provide a connection to apower source as an Edison base (multiple sizes), Plug in, Bi-pin, orBattery connected connection (including water activated battery), etc.The connector 100 would conduct the electrical current through to the ACto DC converter 102. In some embodiments, such as the IntelligentIlluminating Strip (II Strip or Smartstrip) 900 (FIG. 9), the fastenerand power connection means of the connector 100 might be separated. Forexample, an electrical plug is connected via a wire to the rest of theSmartstrip and the Smartstrip is fastened in some other manner (such asscrews or adhesive) to a surface. In other embodiments, such as theIntelligent Illuminating Bulb (II Bulb) 1800 (FIG. 18), the connector100 would be an Edison base or bi-pin for which when the connector isinserted into the appropriate light socket, the connector 100 wouldprovide appropriate contact to extend the AC or DC power source orsupply into the body of the II Bulb 1800. In addition, the connector 100might provide some structural stability in fastening the II Device 140to a surface.

The AC to DC converter 102 receives power from the connector 100 andoutputs the appropriate DC power to the DC/DC converter 104, the LEDcurrent controlling 120 circuit, and LED circuit 122. Note that a singleAC to DC converter 102 can be used in place of the combination of the ACto DC converter 102 and the DC/DC converter 104. The exact power inputmight vary depending on country specific standards or power sources, butas a universal converter, the power output will always be DC voltagesuch as 12 VDC or 18 VDC or 24 VDC. Examples of power inputs include ACpower 60V-290V/45-65 Hz or (Examples: 230 VAC/50 Hz (European/IndianStandard), 110 VAC/60 Hz (US Standard), or a range of DC power from 12VDC to 1000 VDC. The AC to DC converter 102 might be housed within theconnector 100 or separate from the connector 100, depending on thespecific II Device embodiment.

The DC/DC converter(s) 104 receives a power input from the AC/DCconverter 102, it then converts that power to DC power(s) required fordriving the internal components/modules of the II Device 140. Thesecomponents include the controller/processor 106, memory 108, the realtime clock (RTC) circuit 110, the wireless transceiver circuit 112,antenna 114, and possibly components within the LED current controlcircuit 120. It might also supply power to other components, such as thehard reset circuit 116, the ambient light sensor circuit 118, and otherpotential added circuits. There might be multiple converters dependenton the output DC voltages required by different component requirements.Similarly, the power output would very dependent on the exact componentrequirements, for example the output might be 5 VDC, 3.3 VDC, or 1.3VDC.

The controller/processor 106 processes signals received from the memory108, the real time clock (RTC) circuit 110, and the wireless transceivercircuit 112. It might also process signals from other components, suchas the hard reset circuit 116, the ambient light sensor circuit 118, andother potential added circuits. It also takes action and sends commandsto the memory 108, the real time clock (RTC) circuit 110, and thewireless transceiver circuit 112. It might also take action and sendsignals to other components, such as the ambient light sensor circuit118 and other potential added circuits. In one embodiment, the computerprocessor includes a real time clock, processor 106, and memory chip.

The processor 106 processes the signals received by the various othercomponents of the embodiment, computes necessary actions, and sendssignals back out to various other components of the embodiment. Theprocessor 106 will vary in terms of power, speed, and size in differentembodiments. Additionally, the processor 106 is not limited to thecontents listed above and may include other components.

The memory 108 stores data from factory defined settings and from userdefined settings. The controller/processor 106 will read/write data inmemory 108. Data might include factory-defined settings, such ascommunication protocols, identification and security protocols, andother data. Data might also include user-defined settings, such as userprofiles, default commands, programs, and other data. The memory 108could be inside the processor 106 and/or external to the processor 106as a different integrated circuit or chip(s). The controller/processor106 and memory 108 circuits might take a number of different technicalspecifications. In one embodiment, the processor 106 includes a realtime clock, processor, and memory chip. The memory 108 receivesinformation from the processor 106 and stores the commands for retrievalby the processor 106.

The real time clock circuit 110 includes a battery and a date and timeclock based RTC. The controller/processor 106 will set the date and timedata in the RTC 110 and also read the date and time data from the RTC110. The RTC 110 could be internal to the controller/processor 106 or itcould be an external circuit with respect to the controller/processor106. The RTC 110 will run on the DC/DC power unless no power isprovided, in which case it will run on the battery included within thereal time clock circuit 106. The battery could be a rechargeablebattery, in which case the DC/DC power when supplied would also chargethe rechargeable battery through recharging circuitry. The battery couldalso be a non-chargeable battery. In one embodiment, the processor 106includes a real time clock, processor, and memory chip. The real-timeclock is battery powered and could be set for any time and date.

The wireless transceiver circuit 112 allows the II Device 140 tocommunicate with other wireless devices and/or other II Devices. Thewireless transceiver circuit 112 includes a transmitter and receivercircuit based on established wireless protocols. These protocols coulddiffer based on different II Device embodiments and changing wirelesscommunication standards. Example wireless protocols include but are notlimited to Bluetooth, ZigBee, Wi-Fi, and their related variants. Thewireless transceiver circuit 112 will be connected to thecontroller/processor 106 and the antenna 114. In one embodiment, thewireless transceiver circuit 112 is composed of a transmitter andreceiver circuit based on Bluetooth protocols. In other embodiments, thewireless transceiver circuit 112 might utilize other protocols includingbut not limited to ZigBee, WiFi, infrared, WiMax, LTE, ZWave, or otherprotocols not listed. In other embodiments, the wireless transceivercircuit 112 might include other component parts or circuitry.

The antenna 114 captures wireless communication signals and passes themto the wireless transceiver circuit 112 to decode those signals. Theantenna 114 could take multiple forms depending on the protocol andsignal frequency required. The physical location of the antenna 114and/or wireless transceiver circuit 112 could be placed in multiplephysical locations related to the II Device 140. For example, it mightbe placed outside of the II Device 140 or inside the II Device 140.Placing it outside, might increase the range of wireless communicationfor the II Device 140, especially when installed in locations with poorreception. Alternatively, the antenna might be built into the physicalstructure of the II Device 140 or be part of the main board 134 insidethe II Device 140.

In some embodiments, the hard reset circuit 116 of the II Device 140includes a button or switch mechanism and related circuitry. The buttonor switch would be connected to the controller/processor 106 eitherdirectly on the same board or through a wired connection. When thebutton or switch is activated, it will send a specific signal to thecontroller/processor 106 to execute the hard reset program for that IIDevice 140. The actual button or switch mechanism might be differentdependent on the II Device 140 and its application. As example, thereset circuit might be a simple resistant button type switch, it mightbe a rotational type switch, or it might be a conductive type switch, itmight be a compression switch based on pushing in some part of themechanical structure. The location of the hard reset circuit might beco-located with other external components such as the ambient lightsensor, LEDs, diffuser housing, or other II Device components orstructural parts. In this sense the physical location with respect tothe II Device 140 might vary. The hard reset function in mostembodiments will require access to the DC/DC power, and thus the IIDevice 140 would need to be connected to an active power source. In someembodiments though, the hard reset circuit 116 would have access to aseparate power source such as a battery to provide the controller andrelated circuitry enough power to execute the hard reset command.

In some embodiments, the II Device 140 might have an ambient lightsensor circuit 118. The ambient light sensor circuit 118 consists of oneor more ambient light sensors (photosensor or similar light detectingcomponent) and supporting circuit. The ambient light sensor(s) in theambient light sensor circuit 118 detects a level of captured ambientlight, converts that level into an analog signal, and sends that data tothe controller/processor via an analog to digital (A/D) converter thatcould be a part of the ambient light sensor circuit 118 orcontroller/processor 106. The ambient light sensor circuit 118 wouldconsist of one or more ambient light sensors per one or multiple IIDevices. In some embodiments the ambient light sensor circuit 118 couldbe embedded in the II Device 140 itself and in others it might be aseparate peripheral device to the wireless lighting control system.Additionally, the placement of the sensor(s) 118 and related circuitryneed not be exactly collocated, but possibly separated by a wire.

For example, the light sensor(s) 118 could be placed in multiplelocations in relation to the II Device 140: (a) placement of sensor 118requires external light to reach the light sensor; (b) the sensor(s) 118could be placed on the exterior of the light, on the housing; (c) thesensor(s) 118 could be at the end of an extension or wire protruding; or(d) the sensor(s) 118 could be part of an external peripheral to thelight, connected via wireless communication (e.g., the sensor could behoused with other electronic components such as a processor,communication source (Bluetooth module, Zigbee, Wi-Fi, or other)). Therecould also be multiple types of II Device sensors used: (a) one whichsenses a range of overall luminosity; (b) one that senses a combinationof red, green and blue components or cyan, yellow, magenta or blackcomponents, or hue, saturation and lumens components of the light on it;or (c) in different scenarios the light measured could be in absolute orrespective values. The ambient light sensor 118 can be located to detectan ambient light and a light emitted by the II Device 140 such that thecontroller/processor 106 adjusts one or more of the on/off signalsprovided to the LEDs 122.

LEDs 122 refer to a combination of LEDs or LED arms that are illuminateddepending on current passed through from the LED current control circuit120. The combination of LED arms or LEDs could be of various types andvarious colors dependent on the II Device embodiment. For example, theLEDs might vary in color such as red, green, blue, and/or white LEDs.The LEDs might also vary in their maximum output luminosity. Thecombination of illuminations of these LEDs could produce various levelsof brightness and/or color.

The LED current control circuit 120 executes commands from thecontroller/processor 106 to control the current passed through the LEDs122. The LED current control circuit 120 might take different formsdependent on the II Device embodiment as per the following schemes:solely LED drivers scheme (FIG. 3), switches and LED driver scheme (FIG.5), multiplexer and LED driver scheme (FIG. 7), and current limitingcircuit scheme (FIG. 8). In general, the controller/processor 106 sendscommands to LED drivers (208 or 318, 320, 322, 324, or 508), switches ormultiplexer (500, 502, 504, 506 or 702), which in turn controls thelight output by controlling the average current passed through the LEDs122. The average current would affect the overall luminosity of the IIDevice 140, such as that at lower average currents passed through theLED driver then the II Device would be dimmer.

For embodiments where multiple LED arms (302, 304, 306, and 308) arepresent, unique to the presented schemes is a method to maximize thepotential current passed through and subsequent luminosity of each LEDarm with limited available current from the AC/DC converter 102. This isdone by controlling the current passed through by the LED driver (208 or318, 320, 322, 324, or 508) so that only one LED driver (208 or 318 or320 or 322 or 324 or 508) can pass through current at a time. Thisallows each on/off signal to provide a maximum current supplied by theDC/DC power converter to the LED 122. By varying and alternating veryshort lengths of time that current is passed through different LED arms(302, 304, 306, 308) using LED current control circuit 120, the schemesalso allow the multiple LED arms (302, 304, 306, 308) to produce anoverall blended light that is capable of various colors, saturation, andbrightness. These schemes allow the II Device 140 to provide the highestlevel of individual luminosity emitted related to one of the LED arms(302, 304, 306, 308), such as white, red, blue, or green, while alsoallowing for all combinations of color, brightness, and saturation to beachievable.

In other words, the specified color is produced by turning ON the firstcolor LED 122 a for a first portion of the cycle time and turning ON thesecond color LED 122 b for a second portion of the cycle time. The twoor more LEDs 122 are not turned ON at the same time. The cycle time ispreferably short enough such that a user will not notice any flicker,which is usually around 85 Hz (about 12 ms), unless flicker is desired.The on/off signal for the first LED 122 a includes two or more pulsesduring a portion of the cycle time that the first LED 122 a is turnedON. Likewise, the on/off signal for the second LED 122 b includes two ormore pulses during a portion of the cycle time that the second LED 122 bis turned ON. The on/off signals can be adjusted to provide a specifiedcolor, saturation and brightness or intensity. The specified brightnessor intensity can be determined by a duty cycle of the on/off signals.

In one embodiment, the light generator is composed of LEDs, LED Drivers,and a light enhancement cover. The LEDs are of various types and colors.The LED Drivers are the circuitry that drives the LEDs. The LED Driverstake the commands from the processor for turning required LEDs atrequired brightness or intensity.

One potential scheme for the LED current control circuit 120 is the‘solely LED drivers scheme’ (FIG. 3). In this scheme thecontroller/processor 106 would send one or multiple Pulse WidthModulation (PWM) Signals to one or many LED drivers (318, 320, 322, 324)which would control the current flowing through an associated LED arm(302, 304, 306, 308 respectively). There would be the same number of PWMsignals (326/400, 328/402, 330/404, 332/406) sent as there would be LEDdrivers (318, 320, 322, 324) and LED arms (302, 304, 306, 308). Thetotal number of LEDs strings (arms) and LED drivers depend upon theapplication. LED driver circuit is designed for a particular currentlevel to pass through it, so the LED driver circuit (318, 320, 322, 324)will regulate the flow of current through the respective LED arm (302,304, 306, 308) to the set current level whenever the controller 106provides a high level signal to it. PWM consists of high and low signalsat a fixed frequency. One could change the duration of high and lowsignals in a given time frame (defined as time period=1/frequency).Considering the controller sends one PWM signal to one LED driver tocontrol the average current through one associated LED arm. Varying theduty cycle of the PWM signal changes the average current flowing throughthe LED driver to the LED arm. The average current affects the overallluminosity of the II Device, such as lower average currents pass throughthe LED driver then the II Device would be dimmer (i.e., lowering theaverage currents passed through the LED driver dims the light producedby the II Device).

LEDs 122 refer to a combination of LEDs or LED arms that are illuminateddepending on current passed through from the LED current control circuit120. The combination of LED arms or LEDs could be of various types andvarious colors dependent on the II Device embodiment. For example, theLEDs might vary in color such as red, green, blue, and/or white LEDs.The LEDs might also vary in their maximum output luminosity. Thecombination of illuminations of these LEDs could produce various levelsof brightness and/or color.

The heat sink and related components and parts 124 may be required insome embodiments of the II Device 140. The heat sink and relatedcomponents 124 dissipate the heat generated by the LEDs 122 and LEDcurrent control circuit 120. The heat sink 124 could take multiplesizes, shapes, and materials dependent on the II Device embodiment.‘Related components’ refers to the housing and outer structure of the IIDevice 140. These materials and arrangement might of course differdepending on the particular II Device embodiment.

The light reflector 126 is used to amplify or focus the illuminationgenerated by the LEDs 122. The light reflector 126 could be made ofdifferent reflective materials and come in different sizes, dependent onthe specific variation and application of the II Device 140. The lightreflector 126 would be placed behind and/or around the LEDs 122, mostlikely at an arc so that the illumination of the LEDs 122 is reflected,focused, and amplified through the diffuser 128. The exact placement,angle, and arc of the light reflector 126 would vary dependent on thevariation and application of different II Devices.

The diffuser 128 is a part of the II Device 140 that spreads and/or‘mixes’ the illumination produced by the LEDs 122. The diffuser 128could be made of different materials and come in different sizes,dependent on the specific variation and application of the II Device140. Common material might be glass, plastics, or fiber. The diffuser128 would be placed over the LEDs 122 so that the illumination passesthrough the diffuser 128. The exact placement, angle, and arc of thediffuser 128 related to the LEDs 122 would vary dependent on thevariation and application of different II Devices.

The II Device 140 might take other common embodiments not fullydescribed in this disclosure, but not limited to the following: (a) anII Device integrated into a lighting fixture (e.g., could be installedfixture with all II Device circuitries built in or non-installed fixturesuch as a plug in lamp); (b) an II Device integrated into a fan (e.g.,could be installed fixture with all II Device circuitries built in); (c)an II Device that is solely battery powered and affixed to a surface;(d) an II Device utilizing OLEDs as LEDs; (e) an II Device integratedinto directly into surfaces (walls, tables, and ceilings), clothing,appliances, electronics (Displays, music equipment, etc.), musicalinstruments (pianos, guitars, etc.) and taking power from some sourceeither internally or externally to that integrated part; or (f) an IIDevice specifically designed for emergency lighting. Considering thecontrol of the II Device, the invention herein provides processes andmethods to wirelessly control and/or program one or many II Devicesthrough one or many wireless devices. These processes and methods shownand described provide maximum utility and range with a givencommunication protocol and a reliable and efficient system.

As previously mentioned, the II Device 140 could be modular (i.e.,different parts of the II Device 140 as separated by a dashed-dot linesA, B, C, D, E and F could be detachable from a manufacturing or consumerstandpoint). Certain parts or modules of the II Device 140 could beinterchangeable with other types of the same module. As example,consider an II Device 140 that has different connector modules, plug invs. Edison base, yet the rest of the modules are the same. The modulescould be connected together through connectors, that a user couldseparate or place back together. The modules might also be structurallyfixed together so that disassembly is required to disconnect themodules. Additionally, modules within the II Device 140 could beseparated physically from each other yet connected electronically insome fashion. There could be different levels of modularity or nomodularity at all, depending on the specific II Device embodiment.

Given the standard parts and connections of the II Device 140, therecould be numerous potential II Device embodiments with differingarrangements, combinations, or expressions of the components disclosed.Some of these embodiments, characteristics and methods will be describedbelow.

Referring now to FIG. 2, a circuit diagram of a single LED arm 214 withsingle LED(s) 122 in accordance with one embodiment of the presentinvention is shown. The LED arm 214 is electrically connected to thepower supply 200 and the LED driver 208. The power supply 200 and LEDdriver 208 are also connected to the ground or negative terminal 206 ofthe power supply 200. In certain embodiments, the controller/processor106 might send multiple PWM signals 210 to multiple LED drivers 208 tocontrol the current passed through to multiple LED arms 214. In thesecases, the LED current control circuit 120 would allow to similarlychange the overall brightness or luminosity of the II Device 140, butalso adjust the color and/or saturation of the light emitted from the IIDevice 140. In this latter case of controlling color and saturation theLED arms 214 would need to be of different colors that could createdifferent colors when mixed at different levels. The LED arm 214 canhave warm yellow or other colors/types of LEDs 122.

Now referring to FIG. 3, a circuit diagram of a solely LED Driversscheme in accordance with one embodiment of the present invention isshown. For illustrative purposes, consider here four PWM signals (326,328, 330, 332) sent from the controller 106 annotated as PWM1 326, PWM2328, PWM3 330 and PWM4 332 and four associated LED drivers annotated asLED Driver1 318, LED Driver2 320, LED Driver3 322 and LED Driver4 324.In addition, consider four LED arms, LED arm1 302 with red LEDs 310, LEDarm2 304 with green LEDs 312, LED arm3 306 with blue LEDs 314, and LEDarm4 308 with white LEDs 316. Based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller 106 could vary and alternate the length of time that the PWMsignals (326, 328, 330, 332) are sent to the LED drivers (302, 304, 306,308). This would create variations in lengths of time when the LEDdrivers (302, 304, 306, 308) would receive PWM signals (326, 328, 330,332). The length of time would also allow for a similar control in theoverall brightness of the luminosity produced by the II Device 140 inaddition to the control provided by variations of the duty cycle of thePWM signal itself.

Similarly, variations in the length of time that the controller 106would alternatively send each PWM signal (326, 328, 330, 332) to therespective LED driver (318, 320, 322, 324), which would control thecurrent passed through to the respective LED arm (302, 304, 306, 308),would also provide for a combinatory control of the average luminosityproduced by each LED arm (302, 304, 306, 308) and thus allow for controlof color and saturation of the light produced. The frequency of PWMsignals (326, 328, 330, 332) and the rate at which LED drivers (318,320, 322, 324) receive the PWM signals (326, 328, 330, 332) fromcontroller/processor 106 will be high enough (still within the LEDs' andLED Drivers' technical specifications) so that due to the persistence ofvision, consumers would see a constant light output, for example ayellow light instead of fast switching alternate red and green lightoutputs. The scheme in alternating PWM signals (326, 328, 330, 332) doesnot allow for simultaneous PWM signals (326, 328, 330, 332) executed bythe LED driver (318, 320, 322, 324) at the same time. This maximizes thepotential average current passed through LEDs arms (302, 304, 306, 308)and subsequent luminosity of each LED arm (302, 304, 306, 308)considering limited available current from the AC/DC converter 102. Itallows for each LED arm (302, 304, 306, 308) to receive the full powerprovided by the AC/DC converter 102 and regulated by the LED driver(318, 320, 322, 324), such that when it is on all the available currentcould be sent through to the one LED arm.

To further illustrate these concepts, below is an example of how thesolely LED driver scheme might work. Consider, the frequency of PWMsignal is 2 KHz or total time period for one signal (one high and onelow)=½ KHz=0.5 ms. Consider the duty cycle of each PWM1 400 and PWM2 402is the same. The higher the duty cycle, the brighter the overallluminosity would be and vice-versa. Each LED driver (318, 320, 322, 324)is designed for a particular current level, i.e. when LED driver (318 or320 or 322 or 324) is ON (when they get high signal from the controller106), the current passing through the LED driver (318, 320, 322, 324)would be the lesser value of either the designed particular currentlevel or the maximum current that power supply 200 can provide.

Assume that the luminosity created per unit of average current is thesame for both the red LED arm 302 and the green LED arm 304. If in 4 mscycles, the controller turns on the PWM1 and turns off PWM2 every first2 ms and then turns off PWM1 and turns on PWM2 for the next 2 ms withPWM3 and PWM4 are off continuously, then, the overall light output wouldbe yellow (mixture of Red and Green color light, each with sameluminosity).

Referring now to FIG. 4, a timing diagram for the solely LED driversscheme of FIG. 3 is shown. To produce a type of orange light whichconsists of 70% red and 30% Green light mixed together, PWM1/LED Driver1400 should be ON for 70% of the cycle time (here, 70% of 4 ms=2.8 ms)and PWM2/LED Driver2 402 should be ON for remaining 30% of the cycletime (here, 30% of 4 ms=1.2 ms). Similarly, to produce brighter shade oforange light which may consist of 50% RED, 20% Green and 20% White lighttogether, PWM1/LED Driver1 400 should be ON for 50% of the cycle time(here, 50% of 4 ms=2 ms), PWM2/LED Driver2 402 should be ON for 20% ofthe cycle time (here, 20% of 4 ms=0.8 ms), PWM3/LED Driver3 404 shouldbe ON for 0% of the cycle time (here, 0% of 4 ms=1 ms), PWM4/LED Driver4406 should be ON for 20% of the cycle time (here, 20% of 4 ms=0.8 ms),and all PWM/LED Drivers (400, 402, 404, 406) should be OFF for theremaining 10% of cycle time (here, 10% of 4 ms=0.4 ms).

In a similar way, by varying PWM signal duty cycle for four LEDs Drivers(318, 320, 322, and 324) for a given PWM ON/OFF time cycle (4 ms in anexample above), II Device 140 could produce any color with differentshades. When duty cycle is 100% i.e. 100% ON and 0% OFF, the PWM/LEDDriver1 400 and PWM/LED Driver2 402 are ON for 2 ms alternately everyPWM ON/OFF cycle of 4 ms, II Device 140 will produce highest possible(100%) luminosity for the Yellow light. Thus the output luminosity canbe varied by varying duty cycle of the PWM signals (326, 328, 330, 332)to LED drivers (318, 320, 322, 324), providing dimming feature to IIDevice 140.

The algorithm/program in the controller is such that, at a time only oneLED Driver (here, 400 or 402 or 404 or 406) is given a PWM signal. Thisparticular scheme is more useful when power supply has limited currentoutput capability. With such algorithm one could achieve maximumluminosity for any color possible. For example, let's assume a powersupply is rated at a maximum 15V/1 A output and all LEDs have rating of1 A and LED drivers are designed for 1 A current. To achieve 100%luminosity output from RED LEDs, one has to pass 1 A current through REDLEDs Arm 302 continuously. In this case, LED Driver1 318 only will begiven PWM signal for entire 4 ms of the PWM cycle and that too at 100%duty cycle. As against in other design if all four LED drivers aredesigned for ¼th of the possible supply of current i.e. ¼×1 A=0.25 A,maximum current will never exceed 0.25 A through any LED arm, and willthus limit the output luminosity of that particular LED arm.

The algorithm/Program makes sure that only one LED Driver (318 or 320 or322 or 324) has its PWM signal ON at a time. To produce colors, programgives turns ON PWM signals to LED drivers (318, 320, 322, 324) in aserial manner i.e. alternately, fast enough so that due to persistenceof vision, consumer sees the output light as a single defined colorinstead of flickering Red, Green, Blue or White lights.

Now referring to FIG. 5, a circuit diagram of switches (500, 502, 504,and 506) and LED driver 508 scheme in accordance with one embodiment ofthe present invention is shown. In this scheme, the controller/processor106 would send a Pulse Width Modulation (PWM) signal to one LED driver508 which would control the average current flowing through it. Inaddition, there would be a switch for every LED arm between the LEDdriver 508 and each LED arm (302, 304, 306, and 308). The controller isconnected to each switch (500, 502, 504, and 506) and can send an on/offsignal for each. Considering an embodiment with four LED arms (302, 304,306, 308) and subsequently four switches (500, 502, 504, 506), thecontroller 106 would send a signal to control Switch1 500, Switch2 502,Switch3 504 and Switch4 506, while also sending a PWM signal to the LEDdriver 508 to allow current to pass through to the switches (500, 502,504, 506). Variation in the average current passing through the LEDdriver 508 controlled by variations in the PWM sent by the controllerwould increase or decrease the average current passing through to thesubsequent LED arms (302, 304, 306, 308), thus controlling the overallbrightness of the LEDs. The switches (500, 502, 504, 506) turning on oroff, would be able to create different colors and saturation produced bythe light. When a switch (500, 502, 504, and 506) gets high signal fromthe controller 106, it provides path for current to flow from LEDs inLEDs arms (302, 304, 306, 308) to LED driver 508.

Considering the embodiment contains red, green, blue, and white LED arms(302, 304, 306 and 308 respectively), based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller could vary and alternate the length of time that the switchesare turned on. This would create variations in lengths of time when theLED driver 508 would pass through current to the LED arms and thuscreate variations in lengths of time when the LEDs produce light. Thelength of time would also allow for a similar control in the overallbrightness of the luminosity produced by the II Device 140 in additionto the control provided by variations of the duty cycle of the PWMsignal 518 itself.

Similarly, variations in the length of time that the controller 106would alternatively send each switch (500, 502, 504, 506), which wouldcontrol the current passed through from the LED arms (302, 304, 306,308) to the LED driver 508, would also provide for a combinatory controlof the average luminosity produced by each LED arm (302, 304, 306, 308)and thus allow for control of color and saturation of the lightproduced. The frequency of switch signals will be high enough (stillwithin the LEDs' (310, 312, 314, 316) and LED Driver's 508 technicalspecifications) so that due to the persistence of vision, consumerswould see a constant light output, for example a yellow light instead offast switching alternate red and green light outputs.

The scheme in alternating switch signals does not allow for simultaneousswitches being on at the same time. This maximizes the potential averagecurrent passed through and subsequent luminosity of each LED arm (302,304, 306, and 308) considering limited available current from the AC/DCconverter 102 in the power supply 200. It allows for each LED arm (302or 304 or 306 or 308) to receive the full power provided by the AC/DCconverter 102 and regulated by the LED driver 508, such that when it ison all the available current could be sent through to the one LED arm(302 or 304 or 306 or 308).

To further clarify the scheme, consider the following example. A yellowlight with no white light added into it can be produced by thecontroller turning Switch 1 500 ON and Switch 2 502 OFF and then Switch1 500 OFF and Switch 2 502 ON continuously at the same frequency, fastenough so that due to the persistence of vision, consumer sees it as ayellow light output instead of alternate Red and Green light output. LEDdriver 508 circuit can be designed for a particular current level i.e.it will regulate the flow of current through it to the set current levelwhenever the controller 106 provides a high signal to it. PWM (PulseWidth Modulation) 518 consists of high and low signals at a fixedfrequency. One could change the duration of high and low signals in agiven particular time (defined as time period=1/frequency).

An example of how this circuitry works will now be described.Assumptions: (1) frequency of PWM 518/608 set is 2 KHz, i.e. total timeperiod for one signal (one high and one low)=½ KHz=0.5 ms; (2) frequencyat which switches (510, 512, 514, 516/600, 602, 604, 606) are turned ONand OFF=250 Hz, i.e. total time period for switch to turn ON andOFF=1/250 Hz=4 ms; and (3) LED driver 508 is designed for 1 A current,i.e. when any switch (500, 502, 504, 506) and LED driver 508 is ON (whenthey get high signal from the controller 108) current passing through itis 1 A or maximum current that power supply 200 can provide, whicheveris less. The user wants a Yellow light output at half the maximumluminosity possible, for which Red 310 and Green 312 LEDs should beilluminated equally by sending same amount of average current throughthem. Also for half the luminosity, the average current passing throughRED LEDs arm 302 and Green LEDs arm 304 should be half the maximumaverage current possible. This is achievable by turning Switches (510,512, 514, 516/600, 602, 604, 606/500, 502, 504, 506) ON/OFF and settingPWM 518/608 as in the timing diagram below. The power supply can providemaximum current of 1 A for any LED arm (302, 304, 306, and 308) at atime.

Switching frequency of 250 Hz (cycle of 4 ms): When Switch1 500 is ON;Switch2 502 is OFF letting current flow through only one arm at a time.Also, time for which Switch1 500 is ON and time for which Switch2 502 isON are equal, thus producing Yellow light as required. However, toproduce a type of orange light which consists of 70% Red and 30% Greenlight together, SIG1/Switch1 510/600 should be ON for 70% of the cycletime (here, 70% of 4 ms=2.8 ms) and SIG2/Switch2 512/602 should be ONfor remaining 30% of the cycle time (here, 30% of 4 ms=1.2 ms).Similarly, to produce brighter shade of orange light which consists of50% RED, 20% Green and 20% White light together, SIG1/Switch1 510/600should be ON for 50% of the cycle time (here, 50% of 4 ms=2 ms),SIG2/Switch2 512/602 should be ON for 20% of the cycle time (here, 20%of 4 ms=0.8 ms), SIG4/Switch4 516/606 should be ON for 20% of the cycletime (here, 20% of 4 ms=0.8 ms), and all switches (510, 512, 514,516/600, 602, 604, 606) are off for the remaining 10% of cycle time(here, 10% of 4 mA=0.4 ms). FIG. 6 is a timing diagram for the switchesand LED driver scheme of FIG. 5.

In a similar way, by varying the switching combinations for a given timecycle, II Device 140 could produce any color with different shades. Whenduty cycle is 100% i.e. 100% ON and 0% OFF, the LED driver 508 is alwaysON, thus letting current pass continuously through an LED arm (302, 304,306, 308) which has its switch ON, in turn providing highest possibleluminosity for the color produced. Thus the output luminosity can bevaried by varying duty cycle of the PWM signal 518/608 to the LED driver508, providing dimming feature to II Device 140. The algorithm/programin the controller 106 is such that, at a time only one switch or limitednumber of switches will be turned ON. Thus, making sure that maximumpossible current (mainly set by LED driver 508 circuit) flows throughthe LED arm of that particular switch at that time. This particularscheme is more useful when power supply has limited current outputcapability. With such algorithm one could achieve maximum luminosity forany color possible.

For example, let's say a power supply 200 (AC/DC Converter 102) is ratedat a maximum 15V/1 A output. Let's assume all LEDs have rating of 1 A.To achieve 100% luminosity output from RED LEDs arm 302, one has to pass1 A current through RED LEDs arm 302 continuously. In this case,SIG1/Switch1 510/500/600 will be ON continuously and PWM 608 duty cycleto LED driver will be 100% as well. However, if one designs all four LEDdrivers to ¼th of the maximum supply current from AC/DC converter i.e.¼×1 A=0.25 A, maximum current will never exceed 0.25 A through any LEDarm, thus limiting the output luminosity of that particular LED arm andcombination of LEDs to be ON. Algorithm/Program makes sure that only oneLED arm is ON at a time, and to produce colors other than Red, Green,Blue and White, program turns ON/OFF the respective switches fast enoughso that consumer sees the output light as a defined color due topersistence of vision.

Referring now to FIG. 7, a circuit diagram of a multiplexer 704 and aLED driver 508 scheme in accordance with one embodiment of the presentinvention is shown. In this scheme, the controller/processor 106 wouldsend a PWM 518 signal to one LED driver 508 which would control theaverage current flowing through it. In addition, there would bemultiplexer 704 between the LED driver 508 and each LED arm (302, 304,306, and 308). The controller 106 is connected to the multiplexer 704via two signals. Based on SIG1 700 and SIG2 702 signals, the multiplexer704 selects an LED arm (302, 304, 306, and 308) to connect to the LEDdriver 508 at a time producing light with different colors, saturation,and brightness. Variation in the average current passing through the LEDdriver 508 controlled by variations in the PWM 518 sent by thecontroller would increase or decrease the average current passingthrough to the subsequent LED arms, thus controlling the overallbrightness of the LEDs.

Considering the embodiment contains red, green, blue, and white LED arms(302, 304, 306 and 308 respectively), based on established color mixingprincipals, the variation in the luminosity of these four colors couldproduce all color combinations. To achieve this variation, thecontroller 106 could vary and alternate the length of time that themultiplexer signals are turned on to let current pass through to each ofthe respective LED arms (302, 304, 306, and 308). This would createvariations in lengths of time when the LED driver 508 would pass throughcurrent to the LED arms (302, 304, 306, and 308) and thus createvariations in lengths of time when the LEDs produce light. The length oftime would also allow for a similar control in the overall brightness ofthe luminosity produced by the II Device in addition to the controlprovided by variations of the duty cycle of the PWM signal 518 itself.

Similarly, variations in the length of time that the controller 106would alternatively send signals to the multiplexer 704, which wouldcontrol the current passed through from the LED driver 508 to the LEDarm (302, 304, 306, 308), would also provide for a combinatory controlof the average luminosity produced by each LED arm (302, 304, 306, 308)and thus allow for control of color and saturation of the lightproduced. The frequency of signals sent to the multiplexer 704 will behigh enough (still within the LEDs' and LED Drivers' technicalspecifications) so that due to the persistence of vision, consumerswould see a constant light output, for example a yellow light instead offast switching alternate red and green light outputs. The scheme inalternating multiplexer signals does not allow for simultaneous signalsto allow current to pass to more than one LED arms at the same time.This maximizes the potential average current passed through andsubsequent luminosity of each LED arm (302, 304, 306, and 308)considering limited available current from the AC/DC converter 102. Itallows for each LED arm (302, 304, 306, 308) to receive the full powerprovided by the AC/DC converter 102 and regulated by the LED driver 508,such that when it is on all the available current could be sent throughto the one LED arm (302, 304, 306 or 308). The timing method is similarto that of the switches and LED drivers scheme (FIG. 6). The multiplexerscheme would vary dependent on the II Device 140 requirements and totalnumber of LED arms.

Now referring to FIG. 8, a circuit diagram of current limiting circuitscheme in accordance with one embodiment of the present invention isshown. In this scheme, current limiting circuits (800, 802, 804, and806) control the current passed through to each LED arm (302, 304, 306,and 308). There would be as many current limiting circuits as LED armsthat are required for the specific embodiment of the II Device. Thecontroller/processor 106 sends data to the individual current limitingcircuit (800, 802, 804, and 806) and defines the current to be passedthrough to the respective LED arm (302, 304, 306, and 308). A digitalpotentiometer could be used to form the current limiting circuit (302,304, 306, and 308). The resistance of potentiometer is proportional tothe data given to it by controller/processor 106.

For example, to produce a yellow light consisting of 50% Red and 50%Green light at 100% possible output luminosity, DATA1 808 and DATA2 810will set the currents through current limiting ckt1 800 and ckt2 802such that the current splits in half through two arms. For example, ifpower supply 200 is able to provide 1 A current, ckt1 800 and ckt2 802will be set at 0.5 A each. Considering the embodiment contains red,green, blue, and white LED arms (302, 304, 306 and 308 respectively),based on established color mixing principals, the variation in theluminosity of these four colors could produce all color combinations.Setting assigned currents through all circuits (800, 802, 804, and 806),any color, saturation, and brightness within specified limits could beachieved. In other embodiments, the LEDs can be replaced or augmentedwith alternative lighting components and technologies including but notlimited to CFLs, Halogen, and Incandescent.

Referring now to FIGS. 9 and 10, a mechanical diagram and a blockdiagram of a Smartstrip Light 900 in accordance with one embodiment ofthe present invention is shown. There could be numerous versions or likeembodiments, but the general description will be disclosed herein. TheSmartstrip 900 consists of the same arrangement and inclusion of all thecomponents of an II Device 140 as previously disclosed.

The Smartstrip 900 includes a flexible strip 912, an electricalconnector 908 affixed to the flexible strip 912 and two or more LEDs 122affixed to the flexible strip 912 and electrically connected to theelectrical connector 908. In addition, electrical circuitry 906 (DC/DCpower converter 104, controller/processor 106 and LED current controlcircuit 120) is remotely located with respect to the flexible strip 912and electrically connected to the electrical connector 908 via a wire, acable or a connecting strip. The LED current control circuit 120provides an on/off signal having a cycle time to each LED 122 inresponse to one or more control signals received from thecontroller/processor 106 such that the two or more LEDs 122 produce ablended light having a specified color based on how long each LED 122 isturned ON and/or OFF during the cycle time. As shown, the LEDs 122 areformed into LED Groups 1100 that may include a heat sink 124 attached tothe flexible strip 912, a reflector 126 disposed behind or around thetwo or more LEDs 122, and/or a diffuser or lens 128 disposed above thetwo or more LEDs 122. The LED Groups 1100 are connected in parallel orseries or a combination of both by electrical connections 914.

Other embodiments will include additional components. For example, theadditional components may include: a power supply connector/fastener100; an AC/DC power converter 102 electrically connected to the powersupply connector/fastener 100 and the DC/DC power converter 104; a realtime clock (RTC) circuit 110 communicably coupled to thecontroller/processor 106; a memory 108 communicably coupled to thecontroller/processor 106; a wireless transceiver circuit 112communicably coupled to the controller/processor 106; an antenna 114communicably coupled to the wireless transceiver circuit 112; a hardreset circuit 116 communicably coupled to the controller/processor 106;and/or an ambient light sensor circuit 118 communicably coupled to thecontroller/processor 106. These components were previously described inreference to FIG. 1.

The connector 100 could be one of many connectors that would provide aconnection to a power source. This could be an Edison base (multiplesizes), Plug in, Bi-pin, or Battery connected connection. The connectorwould conduct the electrical current to the AC to DC converter 102through an AC power cord 902, which is an electrical wire for carryingstandard mains power supply.

The AC to DC converter 102 receives power from the connector 100 andoutputs the appropriate DC power to the DC/DC converter(s) 104 and theLED current control circuit 120 and LED strip circuit 912. The AC to DCconverter 102 might be housed within the connector 100 or separate fromthe connector 100, depending on the specific Smartstrip embodiment.

The DC/DC converter(s) 104 receives a power input from the AC/DCconverter 102 and then converts that power to DC power(s) required fordriving the internal components/modules of the Smartstrip 900. Thesecomponents include the controller/processor 106, memory, the real timeclock (RTC) circuit 110, the wireless transceiver circuit 112, antenna114, and possibly components within the LED current control circuit 120.It might also supply power to components, such as the hard reset circuit116, the ambient light sensor circuit 118, and other potential addedcircuitries. There might be multiple converters dependent on the outputDC voltages required by different component requirements. Similarly, thepower output would very dependent on the exact component requirements,for example the output might be 5 VDC, 3.3 VDC, or 1.3 VDC.

The Controller/processor 106 processes signals received from the memory108, the real time clock (RTC) circuit 110, and the wireless transceivercircuit 112. It might also process signals from other components, suchas the hard reset circuit 116, the ambient light sensor circuit 118, andother potential added circuitries. It also takes action and sendscommands to the memory 108, the real time clock (RTC) circuit 110, andthe wireless transceiver circuit 112. It might also take action and sendsignals to other components, such as the ambient light sensor circuit118 and other potential added circuitries.

The memory 108 stores data from factory defined settings and from userdefined settings. The controller/processor 106 will read/write data inmemory 108. Data might include factory defined settings such ascommunication protocols, identification and security protocols, andother data. Data might also include user defined settings such as userprofiles, default commands, programs, and other data. The memory 108could be inside the processor 106 and/or external to the processor 106as a different IC. The controller/processor 106 and memory 108 circuitmight take a number of different technical specifications.

Referring now to FIG. 11, a circuit diagram of LED groups 1100 on aflexible LED strip 912 in accordance with one embodiment of the presentinvention is shown. Here, LEDs 122 are placed group-wise on a flexiblestrip 912 with some distance between them. The distance depends upon therequirements of the Smartstrip light requirements. Each LEDs group 1100might have an individual heat sink and diffuser (to mix colors, in caseof different types if colored LEDs in a group). Each LEDs group 1100 hasone or many LEDs 122 from each LEDs arm 1102 depending upon theSmartstrip light requirements. These LEDs 122 of a particular arm ineach group are electrically connected in a series or parallelcombination of LEDs depending upon the requirements of the Smartstrip900. The LEDs arms 1102 are connected to the positive terminal 1106 andthe negative terminal 206 of the AC to DC converter 102. In addition,the number of LED groups 1100 would depend upon the requirements of theSmartstrip 900.

Now referring to FIGS. 12A and 12B, block diagrams of a front view and arear view, respectively of a LED strip 1224 and extendible LED strip1226 in accordance with one embodiment of the present invention areshown. FIGS. 12A and 12B show that LED groups 1100 are placed a flexiblematerial 912 with some distance between them and connected together inseries, parallel or a combination of both with electrical connections914. There could be an ambient light sensor circuit 118 on the front ofthe LED strip 1224 and extendible LED strip 1226 electrically connectedto the electronic circuit 906. Also, there could be a connector 1200 onboth the ends of the LED strip 1224 and 1226 out of which one 1200 a isused to connect to the electronic circuit 906 and the other 1200 b couldbe used to connect to the extendible LED strip 1226. There could be PWMand/or switching signals from the controller/processor 106 that are usedto drive current control circuit 120 on the regular LED strip 1224 andare carried to the end connector 1200 b of the strip which couldeventually be used to drive current control circuit 120 on extendibleLED strip 1226. In case, of the use of an extendible LED strip 1226 inaddition to the regular LED strip 1224, the power requirement to drivetotal LEDs will increase. That could be taken care by higher powersupply ratings, that is, higher ratings of FIGS. 12A and 12B show thatthe strips 912 have adhesive(s) or fastener(s) 1222 to fasten the stripon a surface such as ceiling or wall. The strip 912 is made up of aflexible material so that it could be routed as required during theinstallation at the site of its use. In addition to the LED groups 1100and other potential components as in the regular LED strip (FIG. 12 a),the extendible LED strip (FIG. 12 b) has its own current control circuit120 to control average current through LEDs 122 on the strip (FIG. 12b).

Some Smartstrip 900 embodiments and versions might have an ambient lightsensor circuit 118. The ambient light sensor circuit 118 may have one ormore ambient light sensors (photosensor or similar light detectingcomponent) and supporting circuitry. The ambient light sensor(s) 118detects a level of captured ambient light, converts that level into ananalog signal, and sends that data to the controller/processor 106 viaan analog to digital (A/D) converter. The ambient light sensor circuit118 would consist of one or more ambient light sensors 118 per one ormultiple Smartstrips 900 and/or II Devices 140. In some embodiments theambient light sensor 118 could be embedded in the Smartstrip electroniccircuit 906 board or on a LED strip and in others it might be a separateperipheral device to the wireless lighting control system. Additionally,the placement of the sensor(s) 118 and related circuitry need not beexactly collocated, but possibly separated by a wire 1206. In addition,some Smartstrip 900 embodiments and versions might have a heat sink(s)124, a reflector 126 and/or a diffuser 128.

Referring now to FIG. 13, a block diagram of the mechanical andelectrical connections for the Smartstrip 900 in accordance with oneembodiment of the present invention is shown. The Smartstrip light 900has four parts: a connector 100, an AC/DC converter 102, an electroniccircuit 906 and LED strip 912. Any two parts could be connected by aflexible wire which would provide flexibility of distance between thetwo parts, routing of the Smartstrip 900 while placing it on thesurface. In addition, any two parts could be connected to each otherwith mechanically inflexible material; in fact combined parts could looklike one part. For example, connector 100, AC/DC converter 102 andelectronic circuit 906 parts could be closely connected to each otherand could look like one part.

Now referring to FIG. 14, a block diagram of an extendible LED strip inaccordance with one embodiment of the present invention is shown. A LEDstrip 912 a can be extended by connecting two or more LED strips 912 band 912 c. LED strip 912 a would have a connector 1400 at its ends whichwould be used to connect another strip 912 b to it. As shown in thefigure, LED strip 2 912 b is connected to LED strip 1 912 a and LEDstrip 3 912 c by a flexible electrical extension 1402, such as anelectrical wire, with connectors 1400 on the ends of the LED strips 912a, 1912 b and 912 c. These connectors 1400 could be of various types,for example, male connector on the right end of the strip and femaleconnector on the left end of the strip. The connections 1400 includecurrent controlling signals from controller/processor 106 driving linesfor LEDs 122 on the strip 912 and LEDs driver signals. In addition, thestrip has LEDs current control circuit 120 to control current throughLEDs 122 as explained in the II Device section.

Referring now to FIG. 15, a block diagram of a LED strip 912 extensionthrough parallel connection in accordance with one embodiment of thepresent invention is shown. The extendable LED strip 912 has LED Groups1504 connected in series with an electrical plug-in connector 1500 viaelectrical connections 1502 (positive) and 1508 (ground), and anelectrical plug-in connector 1506 connected in parallel with the LEDGroups 1504 via electrical connections 1502 (positive) and 1508(ground). Electrical plug-in connectors 1500, 1506 are on the both endsof the extendable LED strip 912. On one end of the LED strip 912, therewould be an intake connector 1500 and on the opposite end of the LEDstrip 912 an outtake 1506 connector. The intake connector 1500 wouldplug into the outtake connector 1506 of the previous LED strip 912(either a regular or extendable LED strip) that would ultimately beconnected in sequence to a regular LED strip and the rest of theSmartstrip components and power source.

In addition to FIG. 15, now referring to FIGS. 16 and 17, block diagramsof a LED strip 912 direct connection in accordance with one embodimentof the present invention is shown. The intake connector 1500 would havemultiple electrical connections passing internally to the strip 912.There would be electrical connections 1502 to extend power through tothe LED groups 1100 in series. There would also be electricalconnections 1502 that would extend the power through to the otherouttake electrical plug-in connector 1506 on the opposite side of theLED strip 912. When this outtake electrical plug-in connector 1506 isnot in turn connected to another intake electrical plug-in connector1500 of another strip, the connection will terminate in the outtakeconnector 1506. The electrical connections 1502 would include groundconnection 1508 and current controlling signals such as PWM andswitching signals from the controller/processor 106 for both theconnection to the LEDs current control circuit 120, LED groups 1100 inseries, and the connection to the outtake connector 1506. Additional LEDstrips could be connected in the same fashion. This number of LED stripsconnecting to each other could be limited by the available power sourceand required current for each strip 912.

As shown in the FIG. 16, the outtake connector 1506 on one strip 912 acould be connected to the intake connector 1500 on another strip 912 bthrough an electrical wire 1604 with similar mating connectors 1600,1602 at its end. This type of connection provides additional flexibilityand routing while extending the number of strip in the Smartstrip. Asshown in the FIG. 17, the connecting wire 1604 might be an affixed partof the connector and Smartstrip or a separate part that could be used asneeded.

Now referring to FIGS. 18 and 19, a perspective view and explodedperspective view, respectively, of an Intelligent Illuminating Bulb 1800also referred as II Bulb in accordance with one embodiment of thepresent invention are shown. The II Bulb 1800 is a lamp or bulb likestructure embodiment of an II Device 140. There could be numerousversions or like embodiments, but the general description will bedisclosed herein. The II Bulb 1800 consists of the same arrangement andinclusion of some or all of the elements described above in reference tothe II Device of FIG. 1.

The II Bulb 1800 includes a housing 1802, a DC/DC power converter 104, acontroller/processor 106 electrically connected to the DC/DC powerconverter 104, a LED current control circuit 120 communicably coupled tothe controller/processor 106 and electrically connected to the DC/DCpower converter 104, and two or more LEDs 122 comprising at least afirst color LED and a second color LED electrically connected to the LEDcurrent control circuit 120. The DC/DC power converter 104, thecontroller/processor 106 and the LED current control circuit 120 aredisposed within the housing 1802, and the two or more LEDs 122 areproximate to or within an aperture 1804 of the housing 1802. A heat sink124 is disposed within or outside the housing 1802. A reflector 126 isdisposed within the aperture 1804 of the housing 1802 and around the twoor more LEDs 122. A diffuser or lens 128 seals the aperture 1804 of thehousing 1802. The LED current control circuit 120 provides an on/offsignal having a cycle time to each LED 122 in response to one or morecontrol signals received from the controller/processor 106 such that thetwo or more LEDs 122 produce a blended light having a specified colorbased on how long each LED is turned ON and/or OFF during the cycletime.

Other embodiments will include additional components. For example, theadditional components may include: a real time clock (RTC) circuit 110communicably coupled to the controller/processor 106; a memory 108communicably coupled to the controller/processor 106; a wirelesstransceiver circuit 112 communicably coupled to the controller/processor106; an antenna 114 communicably coupled to the wireless transceivercircuit 112; a hard reset circuit 116 communicably coupled to thecontroller/processor 106; and/or an ambient light sensor circuit 118communicably coupled to the controller/processor 106. These componentswere previously described in reference to FIG. 1.

The connector 100 would be an Edison base or bi-pin for which when theconnector is inserted into the appropriate light socket, the connectorwould provide appropriate contact to extend the power source into thebody of the II Bulb 1800. In addition, the connector 100 will providesome structural stability in fastening the II Bulb 1800 into a socket.In some alternate versions of the II Bulb 1800 the connector might alsobe a plug-in or battery powered connector. The physical location of theantenna 114 and/or wireless transceiver circuit 112 could be placed inmultiple physical locations related to the II Bulb 1800. For example, itmight be placed outside of the II Bulb 1800 or inside the II Bulb 1800.Placing it outside might increase the range of wireless communicationfor the II Bulb 1800, especially when installed in locations with poorreception. Alternatively, the antenna 114 might be built into thephysical structure of the II Bulb 1800 or be part of the main boardinside the II Bulb 1800.

The LED current control circuit 120 executes commands from thecontroller/processor 106 to control the current passed through the LEDs122. The LED current control circuit 120 might take different formsdependent on the II Device embodiment 1800 as previously described. EachII Bulb 1800 would have some arrangement of LEDs 122 that could vary incolor and type (brightness) depending on different II Bulbs. Varioustypes of LEDs 122 would be placed on a LEDs board 136 in a spaced andarranged fashion and connected electronically to other circuitry asexplained earlier. The LEDs board 136 consists of electrically connectedLEDs 122 placed on a single surface. The combination of LEDs 122 couldbe of various types and various colors. For example, the LEDs 122 mightvary in color such as red, green, blue, and/or white LEDs. The LEDs 122might also vary in their maximum output luminosity. The combination ofilluminations of these LEDs 122 could produce various levels ofbrightness and/or color. LEDs 122 on the board would be arranged so thatthe light from them would mix well forming a uniform color and overalllight from the II Bulb 1800 would spread uniformly in at a particulardegree around the circumference of the diffuser 128. In addition, theLED board 136 might be combined or surround other circuitry such as thehard reset circuit 116 and/or ambient light sensor 118. For embodimentswhere this is the case, the LEDs 122 could take a different arrangementto accommodate for the placement of those circuitries.

Referring now to FIG. 20, a diagram of a LEDs Board 2008 in accordancewith one embodiment of the present invention is shown. As an example ofthe LEDs board arrangement, the white LEDs 2006 could be placed at thecenter of the LEDs board 2008 with red LEDs 2000 on the exterior andblue 2004 and green LEDs 2002 placed in between. In addition, there isan arrangement for electrical contacts 2010, 2012 on the LEDs board 2008at some place as shown. The arrangement can be used to connect sensorssuch as ambient light sensor of the ambient light sensor circuit 118 andthe rest switch of the hard reset circuit 116 on the on the II Device totheir respective circuitry that could be on the main board 134. Thearrangement might be on certain planes such as vertical, horizontal, anddiagonals. In addition, the proportional relationship in the number ofcertain color LEDs to other types could vary dependent on the lightemitted by the LED and the specific embodiment requirements.

II Bulb 1800 may consist of Hard Reset circuit 116 as explained earlier.The location of the hard reset circuit might be co-located with otherexternal components such as the ambient light sensor 118, LEDs 122,diffuser 128, or other II Bulb components or structural parts. In thissense the physical location with respect to the II Bulb 1800 might vary.Now referring to FIG. 55, a potential placement of the photosensor 5502and reset switch 5504 on the light mixing cover/diffuser 128, 5500 thatis on the top of LEDs board 2008 of II Bulb. The heat sink and relatedcomponents and parts 124 are required in some embodiments of the II Bulb1800. As explained earlier the heat sink and related components 124dissipate the heat generated by the LEDs 122 and LED current controlcircuit 120 and it could take multiple sizes, shapes, and materialsdependent on the II Bulb embodiment.

Other ‘related components’ refers to related parts required for thefitment of heat sink and parts required of the housing and inner orouter structure of the II Bulb 1800. These materials and arrangementmight of course differ depending on the particular II Bulb embodiment.

As explained earlier, there would be a diffuser 128 that is a part ofthe II Bulb 1800 that spreads and/or ‘mixes’ the illumination producedby the LEDs 122. There could be an ambient sensor, a part of ambientsensor circuit 118 and/or hard reset button, a part of hard resetcircuit 116 on the diffuser 128, in which case, the diffuser 128 couldbe transparent at that place. Also, the diffuser in that case, may havea through-hole arrangement for electrical and mechanical connections ofthe sensor and button to the II Bulb 1800. In the II Bulb as well, asexplained earlier, the light reflector 126 is used to amplify or focusthe illumination generated by the LEDs.

Referring now to FIG. 48, another embodiment of II Device 140 systemwith the wireless energy receiver 4804 and wireless energy transmitter4802 is shown. The wireless energy transmitter 4802 transmits the energywirelessly to the II Device 140 through wireless energy receiver 4804.The wireless energy receiver 4804 that is connected to II Device 140feeds the energy received to the II Device 140 through its connector 100or directly to the AC/DC converter 102. In this case, the input ratingsof AC/DC converter 102 might be different than the universal ratings asexplained earlier (AC power 60V-290V/45-65 Hz). Wireless energy receiver4804 may have inbuilt AC/DC converter in which case, the DC outputgenerated of wireless energy receiver 4804 is directly given to theDC/DC converter 104.

Referring now to FIG. 56, another embodiment of II Device 140 in theform of LED lighting panel 5600 is shown. The panel is mostly used onthe ceiling for down lighting. It might consist of number of LED groups5602 on the front wall of the panel arranged in horizontal and verticalplanes on LEDs board as shown in FIG. 56. The panel 5600 might alsoconsist of LED groups 5602 on side walls of the panel 5600. The LEDboard could be similar to the LEDs board 2008 explained while describingII Bulb. Each LEDs group 5602 might have various types and colors ofLEDs, for example—Each LEDs group may consist of Red, Green, Blue andWhite LEDs making LEDs Group, in turn LED lighting panel 5600 to producelight with various colors and brightness.

The LED lighting panel, an embodiment of II Device also consists ofother circuitry such as LED Current control circuit 120, Real Time ClockCircuit 110, etc. as explained in FIG. 1. Here, the heat sink eitherconnects to the LEDs through LEDs board or there could be heat transferadhesive(s) (potentially different adhesives for different LED groups)between the LEDs board and heat sink. There could be a common lightmixing cover/diffuser 128 for all LED groups 5602 or multiple lightmixing covers/diffuser for each or multiple LED groups.

All the required electronic circuitry per II Device 140 would be insidethe lighting panel 5600, while the positions of the ambient lightsensor(s) of ambient light sensor circuitries 118 and the reset switchof the hard reset circuit could vary. They could reside on the top/frontwall of the panel 5600, on the side walls of the panel 5600. The ambientlight sensor and the wireless transceiver circuit 112 could also takeother placements as explained earlier. There could be multiple ambientlight sensor circuitries 118 on the LED lighting panel 5600 with lightsensor taking the positions on side walls of the panel 5600 as well.

The panel could have single or multiple connectors 100 of various typesas explained earlier while describing connector 100 in II Device 140. Inaddition, theses connectors could be connected to the lighting panel5600 through an electric cable or AC power cord 902. There would be amechanical arrangement to fit the lighting panel 5600 to the ceiling inthe form of an adhesive, fastener(s), screw-in mechanism or any otherpossible arrangement. The panel could also be used for the recessedlighting i.e. inside the ceiling.

Referring now to FIG. 57, another embodiment of II Device 140 in theform of LED Can, a recessed LED downlight Can 5700 that is mostly usedin ceilings is shown. It might consist of LEDs board 2008 as explainedin II Bulb with LEDs facing downwards while Can is installed into theceiling. The LED Can 5700, an embodiment of II Device also consists ofother circuitry such as LED current control circuit 120, real time clockcircuit 110, etc. as explained in FIG. 1. Here, the heat sink is a partof the Can fixture and is connected to the LEDs through LEDs boarditself or there could be heat transfer adhesive between the LEDs boardand heat sink. There would be a light mixing cover/diffuser 128 for LEDsboard 2008 on top of the Can facing downwards.

All the other required electronic circuitry per FIG. 1 of II Device 140would be inside the lighting Can 5700, while the positions of theambient light sensor(s) of ambient light sensor circuitries 118 and thereset switch of the hard reset circuit could vary as explained whileexplaining II Bulb.

The Can 5700 could have single or multiple connectors 100 of any typesas explained earlier while describing connector 100 in II Device 140. Inaddition, the connector could be connected to the lighting Can 5700through an electric cable or AC power cord 902. There would be amechanical arrangement to fit the lighting Can 5700 inside the ceilingthrough adhesive, fasteners, screw-in mechanisms or any other possiblearrangement.

With a wirelessly connected II Device, it will be important for thedevice application to understand the current status of each II Devicewithin the network. In addition, it would be beneficial for each smartlight or an auxiliary wireless device to know the status and signalstrength of other Smart lights within its proximity. This would providea better user experience and a more efficient lighting control system.

Now referring to FIG. 21, a flow chart of a status request/updateprocess for a wireless device or auxiliary device to II Device inaccordance with one embodiment of the present invention is shown. Thebasic process for a status request from the wireless device or auxiliarydevice shown by element 2100 would begin with block 2102. Upon a statusupdate defined event 2103, the device application will trigger a commandthrough the wireless device or auxiliary device to send a wirelesscommunication to all II Devices in the vicinity 2104. This command willthen get extended through the mesh network 2105 (see communication andmesh network processes for reference in as needed.) Upon receipt 2106,each II Device will both respond to the command with the current statusof that II Device 2108 and extend the responses of other II Devices viathe mesh network 2105. Upon receipt back by the wireless device orauxiliary device, the status information will be interpreted by thedevice application 2110 and either store the information in the deviceapplication memory as an input to execute further commands 2114, triggera second communication or command to the II Device network 2116, or takesome other action 2112. The process completes in block 2118.

Referring now to FIG. 22, a flow chart of a status update process for IIDevice to II Device in accordance with one embodiment of the presentinvention is shown. The basic process for an internal II Device networkstatus refresh from II Device to II Device shown by element 2200 wouldbegin with block 2201. Upon a status update defined event 2202, acommand will be triggered in one or many Smart lights to send a wirelesscommunication to all II Devices in the vicinity 2204. This command willthen get extended through the mesh network 2205. Upon receiving statusupdates sent by other II Devices 2206, the status information will beinterpreted by the II Device(processor) 2208 and used to either storethe II Device ID's received and some associated data of the status in IIDevice's memory 2212, trigger a second communication or command to theII Device network 2214, or take some other action such as reconcilingtime or program differences 2210. The process for II Device to II Devicecompletes with block 2216. The processes described in part 2100 and 2200could be executed in some tandem or integrated fashion dependent on thespecific program or task at hand.

The device application, auxiliary device, II Device itself and relatedII Devices and II Device network could update status information upondifferent defined events, time periods, or processes signified by 2101.For example, upon start-up or launch of the device application a commandcould be sent to gather the status information and subsequent layout ofeach Smart light within the network. As another example, after a definedtime period while the device application is open, the wireless devicecould send a command to gather the status information and subsequentlayout of each II Device within the network. As another example, given adifferent defined time period, each II Device could send a command togather the status information and subsequent layout of each II Devicewithin the network. As another example, during certain programs eitheractively runs through the device application or passively in the IIDevice network, either example b) or c) could be executed at differingtimes to better suit the program or application. Or it could be anycombination of the previously described examples.

The actual status of each II Device may include but not limited to thefollowing information: (a) the ID# and signal strength of other IIDevice within range; (b) the color and/or brightness at which the IIDevice is currently illuminated; (c) the status of programs, defaults,and profile information stored in the II Device's memory; and (d) thecurrent time/date as stored in the RTC.

There are a number of different potential processes and programs thatwould require the current status of the II Devices communicated. For thedisclosure of this invention, it will be assumed that the status of theII Devices will already be known if having the status of one or thenetwork of II Devices is generally required to execute the program orprocess. In many cases the process of obtaining the status of an IIDevice is included in description and drawings. In other cases, thestatus need not be required in the program or process.

Now referring to FIG. 23, a flow chart of a communication process from adevice to II Device in accordance with one embodiment of the presentinvention is shown through element 2300. The process begins with block2301. Given a wireless device (WD) is equipped with hardware and systemsto execute wireless communication protocols (Bluetooth, Wi-Fi, ZigBee,or any other wireless protocol) as well as an appropriate deviceapplication 2302, a user could send a lighting command to an II Deviceby selecting the command via the device application 2304. Upon theuser's selection of a command for a specific II Device, the deviceapplication would translate the user's requested command into a lightsetting command and the specific stored ID for the selected II Device2306. This light setting command would include instructions for thespecified II Device ID to execute such as on/off, color, brightness, ora program. The light setting command would be translated into theappropriate wireless communication protocol and wirelessly sent via thewireless device 2308. The II Device if in range of the wirelesscommunication or mesh network 2309 relay communication would receive theprotocol via the II Device's antenna 2310. The transceiver/receivercircuitry would decode the wireless protocol to find the light settingcommand and send that to the controller/processor 2312. The controllerwill execute that command with the respective II Device's relatedcomponents 2314. Upon successful execution, the II Device will respondthrough the appropriate wireless communication that it has executed thelight setting command 2316-2318. The process ends with block 2320.

Referring now to FIG. 24, a flow chart of a communication process from adevice to multiple II Devices in accordance with one embodiment of thepresent invention is shown referred to as element 2400. The processbegins with block 2401. Similar to the process of sending a lightsetting command from a wireless device to an II Device 2300, given anappropriate wireless device and device application 2302, a user couldselect a command for multiple II Devices via the device application 2402that would send a wireless communication through the wireless devicepertaining to multiple II Devices 2404, 2406, which could be extendedthrough the mesh network 2407. Upon receiving the wirelesscommunications 2408, the II Devices could decode 2410, execute thecommand 2412, and each respond to verify the command has been executedutilizing the appropriate communication methods shown as 2414-2416. Theprocess would end with block 2418.

Now referring to FIG. 23 as well as FIG. 24, similar to the process ofsending a light setting command from a wireless device to an II Device2300 and the process for sending a light setting command from a wirelessdevice to multiple II Devices 2400, a user could use multiple wirelessdevices or a combination thereof to send a command to one or multiple IIDevices. As long as the wireless devices have the appropriate wirelessprotocol and associated hardware, has some version of the deviceapplication with an authorized profile 2302, and is in range of the IIDevice (or mesh network), then the wireless devices could send a commandin the same way that one wireless device could, to one or multiple IIDevices.

Now referring to FIG. 25, an II Device 140 within a mesh network (alighting system) will be described. The ability for one II Device toreceive a wireless communication from a wireless device equipped withthe device application, and pass on the communication to another IIDevice to execute the command within the wireless communication. On abroader scale, having a network of II Devices be able to extend andrelay a wireless device's command to extend the signal range or gobeyond the limited number of devices it can communicate with directly orone-to-one. Additionally, have the II Devices within the network confirmthe execution of the command and possible automated or user guidedtroubleshooting steps.

Consider a wireless device (WD) (2550, 2552, 2554) is equipped withhardware and systems to execute wireless communication protocols(Bluetooth, Wi-Fi, ZigBee, or any other wireless protocol) as well asthe installed device application. Each wireless communication system hassome limitation in terms of range (measured in meters or feet). WD1 2550can communicate with II Device1 2500, II Device2 2502 and II Device32504 directly, however, it cannot communicate with other II Devicesdirectly because of range limitation. WD1 2550 can communicate with IIDevice4 2506 by passing the commands and data through II Device3 2504.Similarly, by passing commands/data through II Device3 2504 and IIDevice4 2506, WD1 2550 and II Device5 2508 can communicate with eachother. In the diagram, WD1 2550 can communicate with each II Devicedirectly or through II Device(s). The diagram is an example of meshnetwork with which the controlling wireless device (WD in this case) cancommunicate with all II Device(s) able to communicate with each other.

In diagram above the II Devices are divided in different network levelsas follow: (a) II Devices which are in direct vicinity of WD1 2550 arenetwork level 1 called as NWL1 where II Device1 2500, II Device2 2502,II Device3 2504 are NWL1 II Devices; (b) II Devices which are in thevicinity of NWL1 II Devices, but not in direct vicinity of WD1 2550 arenetwork level 2 called as NWL2 II Devices where II Device4 2506 is NWL2II Device; (c) II Devices which are in the vicinity of NWL2, but not inthe vicinity of WD1 2550 or NWL1 are NWL3 II Devices where II Device52508 and II Device1 2512 are NWL3; and (d) similarly, II Device6 2510 isNWL4 II Device.

The process for forming a mesh network will now be described. There aremultiple processes that the wireless device and network of II Devicescould communicate with each other to set-up a mesh network, dependent onthe size of the network (number of II Devices), the dispersion inlocation of the II Devices (power signal), and other factors. Theprocess would generally involve the wireless device communicating withall II Devices within its signal range, and having each II Device alsocommunicate to other II Devices within its signal range, with anultimate output sent back to the wireless device including the currentstatus and ID's of all II Devices in signal range for wireless deviceand each II Device within the network.

WD1 2550 communicates with NWL1 II Devices and stores their ids andstatuses in the memory 106 and creates a network among them. Each IIDevice also communicates with other II Devices and stores their ids andstatuses in the memory 106 and creates a network among them. WD1 2550then sends commands to NWL1 II Devices asking what other II Devices theycan communicate with and their ids and statuses. Each NWL1 II Deviceresponds to the commands and provides information on theirconnections/network with ids and statuses. WD1 2550 then sends commandsto NWL2 II Devices through respective NWL1 II Device to get theinformation on the II Devices in their network and their statuses. NWL2II Devices responds back to WD1 2550 through respective NWL1 II Devicewith their network information. WD now has all II Device ids in itsmemory at NWL1, NWL2 and NWL3 levels. In the same fashion, WD1 2550continues to build its network map by sending commands to next networklevel II Devices (in this case, NWL4) through intermediary network levelII Devices and gets information on their network. This process wouldcontinue until either the wireless device receives information from alllights set-up within the device application or selected for a particularcommand, or until all II Devices that can be reached through the meshnetwork have been captured either directly or through the mesh networkto the wireless device.

Using the statuses and information from each II Device, the applicationdevice run on the wireless device 2550 would then create a map of theentire network, including what II Devices are connected to what IIDevice and each connection's signal strength, and store it into itsmemory 106. WD1 2550 can find out the most effective path to communicatewith a particular II Device in the mesh network depending upon thesignal strengths between WD1 2550 and that particular II Device andsignal strengths between WD1 2550 and other II Devices wirelesslyconnected to other II Devices and that particular II Device. E.g. indiagram above, signal strength between WD1 2550 and II Device8 2514 isvery low. This may cause communication errors between WD1 2550 and IIDevice8 2514. Therefore, WD1 2550 can chose to communicate with IIDevice8 2514 through II Device2 2502 as signal strength between WD1 2550and II Device2 2502 and that between II Device2 2502 and II Device8 2514is good, leading to less errors in communication. When a command is sentfrom the wireless device to an II Device through a mesh network, the IIDevice will respond to confirm the command has been executed in asimilar path or along a more effective path given any potential changesin the network based on any changes in terms of movement of wirelessdevice, signal strength, etc. The mesh network could be limited to NWL1or NWL2 or any other network level based upon the criticality ofapplication and different II Device embodiments.

Considering the fact that some types of communication protocol/methodshave a limit to the number of devices that can be connected or havecommunication among, the device application will intuitively take theseas input constraints to the formation of an optimal mesh network andpath for the wireless communication of a command. As example, if thewireless communication uses Bluetooth technology, there might be someconstraints. Considering a piconet topology (ad-hoc computer networkusing Bluetooth technology), a master Bluetooth device (Mostly aWireless Device or II Device in this case) can communicate with amaximum of seven Bluetooth devices at a time. Understanding thisconstraint, the wireless device(s) and II Devices could execute the meshnetwork process in such a way to optimize both the total number of IIDevices captured by the network and the path to send any specificcommand through the mesh network. This can be achieved by executing thestandard mesh networking process, and the device application consideringthe resulting map of the network to calculate and decide which specificII Devices to keep connected within the direct connection of thewireless device and which to keep connected through other II Devices.

Considering a case where more than seven II Devices are found within thevicinity of the wireless device, the device application after receivingthe initial network mapping would adjust which II Devices to directlyconnect to and which to connect to through another II Device to attemptto reduce the number of II Devices directly connected to the wirelessdevice. This would open up the ability of the wireless device to searchfor and connect to additional II Devices within initial proximity thatmight not have been able to connect before due to the limit of sevendevices. This process would be balanced to ensure those lights thatcould only connect through another II Device are also accounted for andsignal strength is at the highest possible levels. Note that thisconstraint might not be the case for all versions of Bluetooth topologyor technology.

The steps for forming a dynamic mesh network will now be described.Similarly to controlling multiple II Devices with multiple devices,multiple wireless devices, in this case, WD1 2550, WD2 2552 and WD3 2554could control one or many II Devices via the mesh network. Each wirelessdevice, in this case, WD1 2550, WD2 2552 and WD3 2554 would execute themesh network process in relation to its location as explained earlierwith reference to wireless device WD1 2550 and II Devices in itsvicinity at different network levels such as NWL1, NWL2 and NWL3.

Along the same lines, a dynamic mesh networking is required as awireless device (WD) can move from one place to another changing foritself the II Devices in NWL1 and possibly the II Devices in otherrelated network levels such NWL2, NWL3, etc. In the dynamic mesh networkprocess, the wireless device and II Devices follow the same process asexplained in the formation of mesh network, but the process is repeatedon a continuous basis. Specifically, the wireless device and eachrelated II Device would keep updating their individual network asexplained earlier after every defined time interval. Each II Devicewould also keep providing the ids and statuses of II Devices in itsnetwork to the wireless device(s) in a defined time interval. This timeinterval would vary from a few seconds to hours depending upon thecomplexity and criticality of the application being run, powerconsumption, dispersion of II Devices, and total no. of wireless devicesand II Devices in the network.

In FIG. 25, accessing an II Device network through various devices inaccordance with one embodiment of the present invention is shown aswell. Different types of wireless devices could work together to form,extend, and translate different communication methods to support themesh network. These different wireless devices could be standardwireless devices such as smartphones, tablets, computers, or otherstandard controlling wireless devices with the device applicationloaded. Alternatively, these different wireless devices could be anauxiliary device with some specialized or standardized deviceapplication to either perform a specific function or general function inrelation to the mesh network.

As example, a wireless device located outside of direct contact with thelighting network, but within range to another wireless device withinrange of the lighting network, could send commands through the wirelessdevice to the lighting network and subsequent mesh network. In thiscase, the remote wireless device RD 2548 would originate the commandsand then the localized wireless device WD1 2550 would act as the firstnetwork level of the mesh network. Note that the communication methodbetween the remote wireless device RD 2548 and the localized wirelessdevice WD1 2550 might be different than the communication method betweenthe localized wireless device WD1 2550 and the II Devices lightingnetwork. As an example, the remote wireless device (RD) 2548 maycommunicate with the localized wireless device WD1 2550 via an internetbased protocol while the localized wireless device WD1 2550 communicateswith the lighting network via a Bluetooth protocol. Also, remotewireless device (RD) 2548 could be another embodiment of IntelligentIlluminating Device 140.

Additionally, the remote wireless device RD 2548 might send acommunication to the localized wireless device WD1 2550 to send aspecific communication to the lighting network upon some defined event.In addition, the remote wireless device RD 2548 need not necessarily beoutside of the range of the lighting control system. The wireless deviceWD1 2550 may also act as a specialized auxiliary wireless device such asan external ambient light sensor and communicate with other wirelessdevices.

The Real Time Clock inside of each II Device would need to beperiodically updated to ensure accuracy. To achieve this, the deviceapplication on the wireless device would refer to and share its owncurrent date and time information via the wireless communication andconnection process—either as part of the status update process or analternate process. Additionally, the II Devices themselves can updateand reconcile discrepancies within the date/time without the wirelessdevice itself being present in the network. The actual process to updatethe date/time setting of the RTC in an II Device from the wirelessdevice/device application might be executed in a number of differentways.

The following are potential but not limited to all examples of how adevice to II Device date/time update process would be triggered,generally represented as element 2602. The wireless device/deviceapplication might send the date/time setting upon every command sent tothe II Device network, and when received the II Device(s) would updatethe current date/time setting in the RTC and store latest updatedate/time in the II Device's memory. The wireless device/deviceapplication might periodically over some time or number of processessend the date/time setting upon every command sent to the II Devicenetwork, and when received the II Device(s) would update the currentdate/time setting in the RTC and store latest update date/time in the IIDevice's memory. The wireless device/device application might send thedate/time setting only when specific programming commands are sent oractive that requires information from the RTC and store latest updatedate/time in the II Device's memory. The wireless device/deviceapplication might send the date/time setting after some time setting ischanged within the wireless device/device application. Further, anycombination of the above might be applicable.

Similarly, the process where II Devices share and reconcile date/timesettings might be executed in a number of different ways. The followingare potential but not limited to all examples of how an II Device to IIDevice date/time update process would be triggered, collectivelyrepresented as element 2702. The II Devices might share and reconciletheir date/time at some multiple of when their status is shared. The IIDevices might share and reconcile their date/time only when executingcertain commands or processes. The II Devices might share and reconciletheir date/time after some defined period of time. The II Devices mightshare but only reconcile their date/time when they are different. The IIDevices might reconcile the date/time based on the most recent update ofdate/time setting. Further, any combination of the above might beapplicable.

Now referring to FIG. 26, a flow chart of a wireless device updatedate/time process in II Device in accordance with one embodiment of thepresent invention is shown and referred to as element 2600. The actualreconciliation process and dependency in commands would proceed asfollows, beginning with block 2601. Anytime the wireless device sends adate/time update to any number of II Devices 2604, 2606, the II Devicewill update and match its internal time via the II Device's RTC andmemory 2608, 2610. The II Device's memory will also update the date/timevalue as the original date/time when the RTC was updated 2608, 2612. TheII Device would then confirm the execution of the date/time update backto the wireless device 2614, 2616. In some cases, the wireless devicemight execute a troubleshooting process if not all II Devices confirmexecution of the date/time status update 2618, 2620. The process wouldconclude with block 2622.

Referring now to FIG. 27, a flow chart of an II Device update date/timein II Device in accordance with one embodiment of the present inventionis shown and referred to as element 2700. When an II Device to II Deviceevent occurs as referred to previously as 2702, either through a statusupdate or solely a date/time communication, the II Device(s) would senda date/time communication out to any II Devices either directly withinrange 2704 or within range through the mesh network 2705. When an IIDevice(s) receive the date/time communication from another II Device2706, the receiving II Device will compare the receiving date/timeupdate to its own date/time status in the RTC 2708. If the receiveddate/time communication was set more recently than that of the IIDevice's 2710, then the receiving II Device will update and match itsinternal time via the II Device's RTC and memory 2714, 2716. The IIDevice's memory will also update the date/time value when the RTC wasupdated 2714, 2718. If the values are the same or the received date/timewas updated later than the receiving II Device's internally storeddate/time 2710 to 2712, then the II Device takes no action 2712 and willcomplete the II Device to II Device date/time communication process2720. Considering a mesh network system where there are numerous pathsand scenarios, broadly the II Device's themselves will only update theirdate/time when the received date time originated from a more recentdate/time update. Originated refers to the specific date/time when awireless device sends an update to the II Device(s). If an II Devicethen passes that date/time on to another II Device, the originated datewould still refer to the original date/time when the wireless devicesent the update to the II Device(s).

Referring now to FIG. 28, a flow chart of basic control areas inaccordance with one embodiment of the present invention is shown andrepresented by element 2800. Using the device application on a number ofdifferent wireless devices, a user could communicate and control thewireless lighting system in a number of ways. A user could control asingle II Device, a combination of II Devices, a predetermined group ofII Devices, multiple groups of II Devices, and the whole set-up ofnetworked II Devices. Control pertains to adjusting brightness, color,running a program, or setting a program to run at a future time or uponsome event. All processes begin with block 2801 and continue as follows:

Controlling a single II Device through the application: (a) a user willnavigate through screens on the application to select 2802 an individualII Device (e.g., can arrive by ‘drilling down’ into a group or selectingthe unique II Device to control); (b) once the single II Device isselected 2804, the device application will display potential options forcontrol 2806; (c) potential options for control include but are notlimited to the following collectively signified by 2808: (i) turningon/off to default, (ii) changing brightness, saturation, and/or color,and (iii) running a program now or upon some condition such as time.Alternate options for user customization include but are not limited to:(i) adding the II Device to an existing or new group, (ii) viewing theII Device's group assignments, (iii) viewing a hierarchy of programs andscenes that the II Device is included in, and (iv) troubleshooting theII Device. Once a user has selected the option for control, the deviceapplication will interpret the selection into a light control settingfor the selected II Device 2810 and send a wireless communication viathe appropriate processes, represented here collectively by element2812. As such, once the individual II Device receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriatecommunications processes.

Controlling multiple II Devices through the application: (a) a user willnavigate through screens on the application and select multiple IIDevices 2802 (e.g., can arrive by ‘drilling down’ into a group orselecting the unique light IDs to control; (b) once the II Device IDsare selected 2814, the user will be given options for control 2816; (c)potential options for control include but are not limited to thefollowing collectively signified by 2818: (i) turning on/off to default,(ii) changing brightness, saturation, and/or color, and (iii) running aprogram now or upon some condition such as time. Alternate options foruser customization include but are not limited to: (i) adding the IIDevice to an existing or new group, and (ii) troubleshooting the IIDevice. Once a user has selected the option for control, the deviceapplication will interpret the selection into a light control settingfor the selected II Devices 2810 and send a wireless communication viathe appropriate processes, represented here collectively by element2812. As such, once the individual II Device receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriatecommunication processes represented by 2812.

Controlling a group or multiple groups of II Devices through theapplication. A user will navigate through screens on the application andselect a group or multiple groups of II Devices 2802. Groups of IIDevices will be user configurable combinations of individual II Devices.They will most closely relate to rooms, but can have multiplecombinations. Once the group 2820 or groups 2826 are selected, the userwill be given options for control 2822, 2828, including but are notlimited to the following collectively represented as element 2824 for agroup or 2830 for multiple groups: (i) turning on/off to default, (ii)changing brightness and/or color, (iii) running a program now or uponsome condition such as time, and (iv) turning on/off a program that isset to run in the future or upon some condition.

Alternate options for user customization include but are not limited to:(i) drilling down into individual II Devices for control, (ii) addingthe group to an existing or new group, (iii) viewing a hierarchy savedsettings, programs, and scenes that the group is included in, and (iv)troubleshooting the group. Once a user has selected the option forcontrol, the device application will interpret the selection into alight control setting for the each II Device within the selected groupor groups 2810 and send a wireless communication via the appropriateprocesses, represented here collectively by element 2812. As such, onceeach II Device within the selected group(s) receives the communication,it will then interpret the instructions and execute the command, thenrelay confirmation back to the wireless device per the appropriateprocesses discussed in the communication processes represented by 2812.

Controlling a whole network of lights through the application is similarin fashion to controlling multiple groups, represented by a similarsequence of elements 2802, 2832, 2834, 2836, 2810, and 2812. All basiccontrol processes end at block 2838.

Programming is a process by which an II Device, multiple II Devices, agroup, or multiple groups can execute a command or sequence of commandsgiven some other event occurs or condition is met. Similarly, an IIDevice, multiple II Devices, group, or multiple groups could be given asequence of commands to execute in sequence at some time interval.Unique to the invention disclosed, a user can create programmedcommands, send them wirelessly to any number of specified II Devices,and the command would execute given a condition being met. The conditionwill generally be related to time, but many types of conditions could beinterpreted into time-based activities. For example, wireless devicesable to access the Internet provide a wealth of potential conditionsthat could be converted to time passed or the wireless device couldpassively monitor the condition and send a command when met.

Generally a condition could be executed through these sources: (a) thewireless device sends a command to any number of II Devices to execute aprogram given a date/time passing or date/time being met (e.g.,simulated sunrise, timer, etc.); (b) the wireless device sends a commandto any number of II Devices to execute a program given some otherconditionally based input directly available to the II Device (e.g.,ambient light sensor program); (c) the wireless device sends a commandto any number of II Devices to execute a program with the conditionbeing met at that time and the action stored in the II Devices memory(e.g., reset process); (d) the wireless device sends a command to anynumber of II Devices to execute a program with the condition being metat that time and the action specified through the command (e.g., starrynight); (e) the wireless device sends a command to any number of IIDevices to execute a program given some other conditionally based inputavailable to the lighting control network is available to said IIDevices (e.g., auxiliary ambient light sensor program); (f) the wirelessdevice sends a command to any number of II Devices to execute a programin coordination with wireless communications/commands providedsequentially through the device application (e.g., music sync); (g) thewireless device runs a program to monitor some condition and upon thatcondition being met sends a command to any number of II Devices toexecute a specified command or sequence of commands (e.g., weatheralerts); (h) any combination or sequential representation of the aboveprogram types.

Creating a program involves similar processes to basic control. A userselects an II Device, multiple II Devices, group, or multiple groups torun a program. The user then selects a program to be run by the selectedII Device(s): (a) there could be predefined suggested programs based onthe items selected (e.g., stored in device application memory); (b) theuser could create their own program; (c) each program will consist of atleast one command to be run when one or more conditions are met, ormultiple commands to be run sequentially or upon further conditionsbeing met (e.g., user to set/select condition); (d) the program can berun at that time or saved to run at a future time (e.g., the program canbe set to repeat on certain dates/times, such as days of the week, everyX days, or any time lapse interval). The command or series of commandsis then sent via the wireless network to each associated II Device(s).This is done through the appropriate wireless communication process.Each II Device(s) then interprets the command or series of commands,executes the command, or stores the command in memory to be executedwhen conditions are met. Similarly, each II Device(s) would confirm theprogram command via the appropriate communication method process.

Now referring to FIG. 29, a flow chart of a programming process inaccordance with one embodiment of the present invention is shown andreferred to as element 2900. Once a program or programs are saved a usercan recall and toggle those programs on/off. The process begins withblock 2901. At the main level of the device application 2902, there willbe a ‘programs’ button. When selected 2904 this will display allprograms associated with the active profile. Each program will be listedwith their current status as active vs. inactive. The programs will besorted based on active vs. inactive status with active listed first.Secondly, the programs will be sorted based on the proximity of theassociated II Devices to each program 2906. When toggled on 2908, theapplication will send the command or series of commands via the wirelessnetwork to each associated II Device(s) 2910 through one or moreappropriate communication processes, collectively represented here as2912. The actual light setting associated with the program might bestored in device application so that the wireless communication is toexecute a specific program type command. The actual light setting mightalso be stored in the II Device itself 2914 so that the deviceapplication/wireless device only requests the II Device to run thatprogram. Each II Device(s) then interprets the command or series ofcommands and their related program conditions, executes the commandgiven a present condition, or stores the command in memory to beexecuted at a later condition time or event. In the latter case, oncethe condition is met the II Device(s) will execute the program command2918. Then if there are further conditional commands within the program2920, the II Device will continue to monitor for conditions until theyare met 2916 and the II Device similarly follows the process to executethe program command 2918. Once no further conditional commands are inthe program 2920, the program completes and changes to inactive status2922 so that the program commands are deleted from the memory of eachrelated II Device, and the program returned to an off status in thedevice application 2924. Alternately, a program that was set to run canbe turned off 2908 so that the wireless device sends a command to therelated II Devices to not execute the conditional command prompted bythe program 2928. This command would be communicated through one or moreappropriate communication processes, collectively represented here as2912. When received, each II Device would change the program to completeand change it to inactive status 2922 so that the program commands aredeleted from the memory of each related II Device, and the programreturned to an off status in the device application 2924. The programmight still be saved in the device application memory for future use, ifa saved program. The program run process ends in block 2930.

In the case where program commands would overlap with each other, thedevice application will prompt the user to confirm the programselection. In such case, the selected program will overlap anyconflicting previously activated program. Alternatively, if the programcommands originated from multiple devices or profiles, the II Deviceswill execute programs in the order of profile hierarchy. Alternatively,the programs might execute in the order of the last received command.

Scenes & suggested scenes will now be described. A scene is a predefinedsetting or program related to multiple II Devices and/or groups, so thatwith one user selection any or all II Devices would execute a specifiedsetting or program. This element is useful to support very holisticfunctional lighting like turning off all II Devices before going to bed,turning on some II Devices to walk to the bathroom, setting a mood fordinner or a movie, or many other personal preferences. A scene iscomprised of a defined light setting and/or program for each of anynumber of individual II Devices and/or any number of groups. When ascene is activated, the device application recalls the defined lightsetting(s) and/or program and the associated II Device (s)/group(s) andsends a standard wireless command to each.

Referring now to FIG. 30, a flow chart of a process for creating a scenein accordance with one embodiment of the present invention is shown. Thescene control selection can be both suggestive and user configurable. Auser could drill into each established scene to view or edit the statesfor each II Device, add more II Devices, etc. A user could also select ascene to be run at a previous time such as through an automationprogram. Scenes might display graphically in the user interface with themost used scenes or the scenes containing the II Devices with theclosest signal strength higher in order. Users could also drag and dropthe order of scenes displayed to their preference.

Once a network of II Devices is set-up, the application might suggestsome pre-configured scenes dependent on the number of II Devices set-upwithin the network and the names of the groups (most likely rooms) thatwere assigned. More specifically, the device application would refer tothe list of groups configured by the user, and if certain predefinedkeywords or combinations of words were found within those groups, theapplication would suggest/show a scene related to that group or groupsin the scene options. Also, the device application would refer to thenumber of II Devices, the number of groups, and the number of II Deviceswithin each group to create suggested/predefined scenes. With more IIDevices, groups, and II Devices within groups, more complex scenes couldbe suggested, or more group specific scenes could be suggested. All # ofII Devices would include scenes all off and all on related to turningall II Devices off within the addressable network, or turning all IIDevices on. As example, for any lighting network containing a group oflights with the word “TV”, “Television”, “movie”, “film”, or relatedword, the application would suggest a lighting scene related to watchinga movie, such as a soft blue light emitted from each of the II Devices.The types of suggested scenes could vary dependent on differentapplications.

Through the device application, the user can create a new scene,referred to as element 3000 and beginning in block 3001, by firstselecting the option to create a scene in the device application 3002and selecting any number of II Device(s) and/or group(s), with which tostart creating the scene 3004. The user would then select/create thelighting control setting or program for the selected II Device(s) and/orgroup(s) II Device. Here, the light setting might be a previously usersaved configuration, an automated application suggested configuration,or a newly created configuration 3006. Once selected, the user wouldthen have the option to add additional subsets of II Device(s) and/orgroups to the scene 3008, which would revert back to a similarconfiguration process for that selection 3004, 3006. Once the user hasconfigured all the II Device(s) and/or group(s) that they wish 3008, thescene, comprised of any combination of II Device(s) and/or group(s),each with a specified light setting or program, will be saved and theuser could assign a specified name 3010. This information will be storedin the device application memory 3012 and the process will end in block3014.

Note that each II Device within the scene is able to have a different IIDevice brightness and/or color. In addition, pre-defined programs for IIDevice(s) can also be run or activated through a scene in combinationwith a specific type of lighting to be executed at that time. Forexample, a ‘time to sleep’ scene might turn off all the II Devices inthe network, except for one II Device on very low blue light in achild's bedroom, and activate the II Device alarms for all bedrooms inthe house for a certain time. Once the user has selected the II Devicesand lighting output, the user can save that scene for future use asreferred to previously in 3010. The scene is saved within the deviceapplication memory 3012.

Now referring to FIG. 31, a flow chart of a process for executing ascene command in accordance with one embodiment of the present inventionis shown as element 3100. The process begins in block 3101. To turn ascene on, when the device application is open 3102, the user wouldselect (switch on) the desired saved (or suggested) scene as an optionpresented in the device application interface 3104. The deviceapplication would then retrieve and convert the scene selection intospecific light setting commands and/or programs to be executed by eachof the related II Devices in the scene 3106. The wireless device wouldthen convert the series of II Device light setting commands or programsinto the appropriate wireless communications directed at each of therelated II Devices within the group 3108. Upon receipt, each II Devicewould execute its related light setting command or program and send theappropriate wireless communication back to the wireless device toconfirm execution of the scene 3110. The process completes in block3112.

Changing and adding unique groupings of II Device (Setting up your owngroups) allows for user configurable set-up, alteration, and assignmentof any number of II Device combinations of the addressable lightingnetwork. Within the device application, each II Device has its ownunique ID. Through the application a user can combine any number of IIDevices and or existing groups together to form a group of II Devices.This can be done through user gestures (dragging and dropping),selecting an individual and assigning to a group, or through theeasy-setup program. Once any number of lights is assigned into a group.A user can select commands to all II Devices within the group by simplyselecting the group.

Referring now to FIG. 32, a flow chart of a process for creating a newgroup or adding to an existing group in accordance with one embodimentof the present invention is shown as element 3200. The process beginswith block 3201. A user selects any number or combination of II Devicesand/or groups through the device application 3202. The user then selectsthe option to either create a new group from the selection or add theselection to an existing group 3204. If creating a new group fromselection 3206: (i) then the user will need to name the group 3208(e.g., the device application might have a list of predefined namingconventions that a user has the option of selecting 3210, or they cantype their own); (ii) the user would then be prompted through the deviceapplication to set a group default light setting for all II Deviceswithin the group 3212 (e.g., a user could select different unique lightsettings for each II Device within the group that are all saved underthe group light setting (see default process for more details); (iii) asthe user is selecting the group default light setting, if in proximityto the actual lighting network the wireless device would adjust therelated II Devices to execute the light settings as the user is togglingdifferent options while selecting a default group setting 3214; (iv)once a user selects and sets the group default light setting 3212, thenthe group setting could be saved 3216 to the device application's memoryto be run in the future 3218 with the process ending in block 3224. Foradding the selection to an existing group 3220: (i) the user would thenselect what group to add the selection to via the device application3222; (ii) the user would then be prompted to confirm extension of thedefault group setting to the newly selected II Devices/groups or createnew light settings for the selected II Devices within the group 3212;(iii) as the user is selecting the group default light setting, if inproximity to the actual lighting network the wireless device couldadjust the related II Devices to execute the light settings as the useris toggling different options 3214; and (iv) once a user selects andsets the group default light setting 3212, then the group setting couldbe saved 3216 to the device application's memory to be run in the future3218 with the process ending in block 3224.

Now referring to FIG. 33, a flow chart of a process for executing agroup command in accordance with one embodiment of the present inventionis shown as element 3300. The process begins in block 3302. User selectsgroup(s) 3304 and related light setting command/program 3306 through thedevice application user interface. The application then identifies theII Devices assigned to the selected group through internal memory 3308.Wireless device running application sends commands through wirelesscommunication for those specified II Devices in the group 3310 followingthe appropriate communication methods/processes. Each II Device receivesand executes the intended light control setting or program 3312. Each IIDevice responds to the wireless device to confirm execution of the groupcommand 3314 following the appropriate communication methods/processes.Upon receipt of all confirmations the device application would updatethe group to ‘active’ or ‘on’ in the user interface 3316 with theprocess ending in block 3318. Note that any individual II Device can beassigned to multiple groups. Multiple groups can be combined, adjusted,or used to create new groups. Also note that in some scenarios not allII Devices assigned to a group could be accessed due to signal rangelimitations or other problems. In these cases, the user would still havethe ability to control those II Devices that are accessible at thattime. Similarly, a notation could be made in the user interfacesignifying a group that is not fully accessible.

A process will now be described for setting, using, and changing defaultlight levels for any number of II Devices (including switching on/offthrough an external switch, such as a wall switch (see FIG. 62)), sothat a user can easily customize, save, and recall their standardlighting preference. Additionally, a process allowing for anyone to turnon the preset default of the II Devices, without using the applicationwill also be described. Each II Device will always have an associateddefault light level. Each II Device might have multiple related defaultlight levels with the following framework. (i) Manufacturing default—foreach II Device the most basic light setting stored in each II Device'sinternal memory. The manufacturing default light setting will always bestored in the II Device's memory. (ii) Light default—for each II Device,the active default light setting that will be executed when the IIDevice is turned on directly as in the process steps of 2800 to 2804 to2838 (not through a group command) or upon power restoration. Each IIDevice can only have one light default. This default light setting isstored within each II Device's memory until the II Device is reset orthe light default is changed. When unassigned, the light default revertsto the manufacturing default. Group default(s)—The light setting thatwill be executed by each II Device within the selected group when theselected group is turned on through the device application. The groupdefault is stored within the device application related to each group.Each II Device is able to execute multiple group defaults, dependent onwhich group the user has selected to turn on and their individualcommands within the group default. During the set-up process, or anytime after installation, a user can change the light default or groupdefault settings through the device application.

The manufacturing default will most likely be a standard high outputwhite type of light. This light setting will be programmed into each IIDevice during the manufacturing process and stored into the II Device'smemory. This default will first be executed when the II Device ispowered on for the first time. As such, the manufacturing default isindependent of the device application. After a light default isassigned, the light default setting will take precedence over themanufacturing default; however the manufacturing default setting willstill stay stored within the II Device's memory. When a light is resetto the manufacturing state, either through the hard or soft resetfunction, the light default will be erased and the II Device will revertback to the manufacturing default acting as the light default.

Referring now to FIG. 34, a flow chart of a process for creating oradjusting a light default in accordance with one embodiment of thepresent invention is shown and referred to as 3400. The process beginsat block 3402. At any time after setting up an II Device with the deviceapplication such as the process described in 3900, a user can select oradjust a personalized light default setting. A user can select one ormore II Device(s) through the device application 3406, adjust the colorand/or brightness 3408 and set that selection as the light default forthe respective II Device(s) 3410. Upon assignment of the light default,the device application via the wireless device will send a wirelesscommunication to the related II Device(s) 3412, through an appropriatecommunication means. The communication will instruct each II Device tostore its respective configured setting in its internal memory as thelight default setting, instead of the manufacturing default orpreviously assigned light default 3414. This communication request willthen be executed by the controller and related components, including thestorage of the new light default in the II Device's memory 3416. Theassigned light default light setting will also be stored in the deviceapplication memory 3418. This would end the process for setting a new orchanging an existing light default setting 3420. The light defaultsetting can be changed or adjusted at any time and would follow asimilar, if not the same, process for creating a new light default asdescribed as element 3400. Each II Device can only have one lightdefault at a time.

Now referring to FIG. 35, a flow chart of a process for creating oradjust a group default in accordance with one embodiment of the presentinvention is shown and referred to as 3500. The process begins withblock 3502. First, the user would select the group to assign or adjust agroup default 3504. This could happen either through selection of anexisting group in the device application 3506 or when a user creates agroup as in the process 3200. A selected group might consist of onegroup or multiple groups together. The user will then need to specifythe particular light setting for that selected group(s) to execute whenturned on as a group 3508. Once a group default is selected for thegroup 3510, the associated light setting for each II Device within thegroup will be stored within the device application 3512, to be executedat that time or in the future. If a group default is set for associatedII Devices that do not have a light default 3514, the group defaultlight setting will also be assigned and communicated to each related IIDevice as the light default light setting 3516. This will most likelyhappen during the initial set-up and grouping process. In this scenario,the device application and related wireless device will execute thewireless command similar to that in setting a light default 3400, andthe group default process will be complete as signified by block 3520.Similarly, if unedited at the light default level, future changes to thegroup default will similarly change the respective light defaultsetting. When an II Device associated with the group already has anassigned light default 3514, but that light default was originally setby creating that same group default that is being configured 3518, thenthe light default will be adjusted as the group default it wasoriginated from is adjusted 3516 and each II Device will execute theprocess to adjust its default light setting with the group default lightsetting as in the process 3400. The group default process will then becomplete as signified by block 3520. If the light default setting didnot originate from the group default being configured 3518, then thelight default will not be updated and the group default process will becomplete as signified by block 3520. When the group default is executedit follows a similar process as that for executing a group command or3300.

Referring now to FIG. 36, a flow chart of a power restoration process inaccordance with one embodiment of the present invention is shown andreferred to as process element 3600. The process begins with block 3602.Anytime an II Device goes from not having an electric current 3604 tohaving an electric current 3606, for any period of time, the II Devicewill execute the power restoration mode 3608. If a light default isassigned to the II Device 3610, the power restoration mode will triggerthe II Device to recall the light default setting from its internalmemory and execute the light default setting 3612. If unassigned 3610,the II Device will recall the manufacturing default setting from itsinternal memory and execute the manufacturing default setting 3614. Inaddition, the power restoration event and/or association in executingeither the light default setting or manufacturing default setting couldact as an input event or condition for specific programs 3616, such asthe quick set-up or quick grouping processes, or as a status definedevent 2101 or part of the II Device's next status update 3618 asdescribed in 2100 or 2200. The process ends with block 3620. This wouldcommonly occur when a light switch is changed from ‘off to on, or fromon to off to on. A user would not need to utilize the device applicationto trigger the light default action in this sense. The power restorationmode, or more simply turning the power source to the II Device off, willcease any currently running (the II Device is executing it at that time)program, scene, or setting, but will not erase any program that isactive (set to be run in the future) and its associated setting from theII Device's memory. A user could choose not to utilize the powerrestoration mode can by turning it off through the user's settings onthe device application.

Now referring to FIG. 37, a flow chart of a process for executing adefault command through an on/off toggle in accordance with oneembodiment of the present invention is shown and referred to as 3700.The process begins with block 3702. A user would select the desired IIDevice(s) and/or group(s) through the device application 3704 andtoggles the basic ‘on’ command related to executing the selection'srespective defaults 3706. When toggled ‘on’ the device application wouldretrieve the appropriate saved default including the related IIDevice(s) and their associated light settings 3708. The wireless devicewould then send an appropriate wireless communication to the IIDevice(s)/group(s) to execute their respective light setting 3710. Eachrelated II Device would then receive and execute the command 3712, andthen it will respond to the wireless device confirming execution of thecommand 3714 following the appropriate communication methods/processes.The process would end with block 3716. A user could turn off or adjustany running default command through the process outline above, 3700.Referring now to FIGS. 38A-F, diagrams of various screens on deviceapplication in accordance with one embodiment of the present inventionare shown. The device application will generally be run on a wirelessdevice such as a smartphone, table, or computer. In these cases, thedevice application will most likely have the below screens and sectionsto support user control of the wireless lighting control system. A usercould toggle between screens through various human computer interactionmethods, dependent on the wireless device, but most commonly will begestures and/or touch selections.

As shown in FIG. 38A, a device 3800 displaying a favorites screen 3802will display a list of user generated favorite commands relating to IIDevices, groups, programs, and scenes. Each item displayed on thescreen, as exemplified by 3804 as one item, would be a specificselection of II Devices and an associated action that could be activatedthrough toggling of the on/off button, represented by 3806. Whenselected, the wireless device and related II Devices will execute therelated communication method for that command. A user can also add ordelete favorite settings through this screen or various other screens,for example a user could select 3808 in the figure to perform thiscommand.

As shown in FIG. 38B, a device 3800 displaying a screen 3818 willdisplay a list of all groups created within the device application'sprofile. Each or multiple groups, as exemplified by one group as 3820,could be selected to turn on to the group default setting, or off;exemplified by the selection of 3822. Each or multiple groups could alsobe selected and then given some specific command or other option asoutlined in the groups section. When selected, the wireless device andrelated II Devices in the group (s) will execute the relatedcommunication method for that command. A user can also select a group toview the individual II Device screen filtered to just that group. A usercan add, edit, and or delete group(s) and default group settings throughthis screen or various other screens, for example a user could select3824 in the figure to perform this command.

As shown in FIG. 38C, a device 3800 displaying a programs screen 3832will display a list of all programs created or suggested (manufacturingdefault programs) within the device application's profile with an on/offstatus for each program. Each program, as exemplified as one program by3834, could be selected to turn on or off, a command potentiallyexecuted by toggling 3836. Additionally, each program could be selected,edited, or deleted. When a program command is selected, the wirelessdevice and related II Devices to the program will execute the relatedcommunication method for that program. A user can add or deleteprogram(s) through this screen or various other screens, for example auser could select 3838 in the figure to perform this command.

As shown in FIG. 38D, a device 3800 displaying a scene screen 3848 willdisplay a list of all scenes created or suggested (manufacturing defaultscenes) within the device application's profile with an on/off statusfor each program. Each scene, as exemplified as one item by 3850, couldbe selected to turn on or off, a command potentially executed bytoggling 3852. Additionally, each scene could be selected, edited, ordeleted. When a scene command is selected, the wireless device andrelated II Devices to the scene will execute the related communicationmethod for that scene. A user can add or delete scene(s) through thisscreen or various other screens, for example a user could select 3854 inthe figure to perform this command.

As shown in FIG. 38E, a configure screen 3860 is used to adjust thecolor 3862, brightness 3868, saturation 3874, and other configurationfor selections of II Device(s), group(s), program(s), and/or scene(s).The configure screen 3860 might be different depending on the selectionand specific type of configuration. In general, the configuration screen3860 will consist of the three level lighting control interface 3850 anda list of the selection (II Device(s)/group(s)) 3852. There would mostlikely be related configuration screens for the selection of programconditions, scene creation/editing, and other more complexconfigurations.

More specifically, certain II Devices with color and white could becontrolled through three levels: color 3862, saturation 3868, andbrightness 3874. This functionality is derived by the capabilities ofthe schemes in the LED controlling circuit and related LEDs andsupported device application. Color levels would be derived by combiningdifferent variations and combinations in the average luminosity passedthrough the II Device's LEDs. A color level selection 3862 refers to aninput on a user interface that would go to create any number of colorsderived from the mixing of the LEDs found in the II Device. The colorlevel could be controlled incrementally or at fixed points, for examplea user could select a color level from a color slider 3864.Alternatively, a user could select specific colors from the color levelsuch as blue, green, red, etc. as represented by 3866.

Brightness levels would be derived by either increasing or decreasingthe average current passed through the LEDs of the II Device, but in thesame proportion as that required for the selected color. The differencein brightness levels would only be apparent in variations in theluminosity of the light emitted from the II Device. The color will stayconstant when adjusting the brightness. Similarly, a brightness levelselection 3868 could be controlled incrementally or at fixed points, forexample a user could select a brightness level from a slider 3870.Alternatively, a user could select specific brightness levels such as25%, 50%, dim, bright, etc. as represented by 3872.

Saturation levels would be derived by adding or subtracting someproportional amount of average current passed through the white LEDswith respect to the average current combinations of the set color. Theoverall effect of increasing the saturation level would be reducing therelative amount of white light produced by the II Device in relation tothe colored LEDs. The overall effect of decreasing the saturation levelwould be increasing the relative amount of white light produced by theII Device in relation to the colored LEDs. Similarly, the saturationlevel selection 3874 could be controlled incrementally or at fixedpoints, for example a user could select a saturation level from a slider3876. Alternatively, a user could select specific saturation levels suchas 25%, 50%, lighter, darker, etc. as represented by 3878. Note that thechange in saturation selected through the device application would notnecessarily have a linear relationship to the amount of white lightadded or reduced, but it could be exponential or through some othercalculation. The overall effect and process would manage the saturationlevels so that the perceived difference is gradual to the user, whilemanaging for the constraint in the amount of current available to theLEDs.

As shown in FIG. 38F, a device 3800 displaying a II Device screen willdisplay a list of all II Devices either selected or identified withinthe device application's profile, the screen represented by 3882. EachII Device, as exemplified as one II Device by 3884, could be selected toturn on or off to the light default, a command potentially executed bytoggling 3886, or configured in some other fashion. Additionally, eachII Device or combination of II Devices could be selected, edited, orgiven some other command or selection as outline in the basic controlsection. When an II Device command is selected, the wireless device andrelated II Device(s) will execute the related communication method, forexample a user could select 3888 in the figure to perform these types ofcommands.

Now referring to FIG. 39, a flow chart of a quick set-up process forconnected lights in accordance with one embodiment of the presentinvention is shown and referred to as 3900. A process that allows an IIDevice or multiple II Devices to quickly and securely establish aconnection with a wireless device and the associated device applicationand with other connected II Devices around it. The process begins inblock 3902. Each II Device when initially purchased or reset will be ina manufacturing state 3904. When in a manufacturing state, uponreceiving initial power (current), the II Device(s) will enter powerrestoration mode 3906 as described in FIG. 36. The II Device(s) willthen be prone to discovery by a wireless device with the associateddevice application 3908. The II Device(s) would also execute themanufacturing default light setting 3910. Upon launch of the quickset-up process on the device application 3912, the wireless device andII Device (s) in the manufacturing state will then identify and connectto each other if within range or through an extended mesh network in themanufacturing state to create a secure paired connection 3914. Thedevice application on the wireless device will then store each detectedII Device's unique ID 3916, so that it can communicate with it in thefuture. Each II Device would similarly recognize and store a unique IDassociated to the user's device/profile 3918, so that only thatsmartphone/profile ID can send directions to the II Device in the future3920. Similarly, the II Devices could send commands and communicate witheach other.

In some embodiments—the set-up process could use different color lightsettings as cues in the set-up process. For example, the II Device woulddisplay a certain color upon initial power up, signaling to the userthat the II Device is not connected to the network. Then uponestablishing connection to a profile, the II Device would change colorsto signal the connection has been established 3922. Next, a user mightconfirm that all II Devices are connected and select an option in thedevice application to move forward with the set-up 3924. If not allconnected, then execute troubleshooting steps with user. Identifyproblem II Device. Execute quick troubleshooting steps 3926—step closer,screw in/secure connection to power source. User can possibly provideconfirmation through the device application that all II Devices are aspecific color. All II Devices become connected, and user selects optionthat II Devices are not all connected, then prompt to select color oflight. Should be color of unpaired light or no light, if unpaired light,ask user to step closer to the II Device and select OK. Then shouldconnect and user can continue set-up. If no light, ask user to make surethat the II Device is firmly screwed in and the light switch is on. Thenproceed through set-up menu. Once user confirms set-up of installed IIDevices 3924, they can continue with any further set-up or customizationprocesses 3928, such as adding names, defaults, and favorites. A usercan repeat this process to continue setting up other II Devices 3930until all intended II Devices are set-up and the quick set-up process iscomplete 3932.

Referring now to FIG. 40, a flow chart of a quick group process throughpower restoration in accordance with one embodiment of the presentinvention is shown and referred to as process element 4000. A quickgroup process through power restoration provides a quick way for a userto combine II Devices into a named group through use of the powerrestoration mode. It could be a guided process within the set-up processof the II Devices network through the device application as described inFIG. 39. It also could be run after the initial set-up of the II Devicenetwork. The process begins with block 4002. Upon launch of the quickgroup process through the device application 4004, though deviceapplication instruction, or in the natural course of set-up, the userwill turn off the power source to the related II Devices that they wouldlike to group, then turn the power source back on 4006. When done, thiswill prompt the related II Devices to enter the power restoration mode4008. This action will most likely be through the use of a wall switch.The II Devices will execute the appropriate default setting as discussedin FIG. 36. The device application and related wireless device will thensearch for all II Devices that have entered the power restoration modethrough various communication methods previously discussed, record theirunique IDs 4010, and display the associated II Devices through the userinterface on the device application or some other type of user feedbackmeans 4012. The user will then be prompted to confirm that the correctII Devices were captured 4014. Could use color cues to help with theconfirmation as discussed in FIG. 49. If user does not confirm, then goto troubleshooting steps 4016. If yes, then continue with the process tocreate a new group 4016 as outlined in FIG. 32. After setting up a quickgroup the user might then be asked if they would like to set-up anotherquick group through the device application 4018. If yes, then repeat thequick group process 4002. If no, then end quick group process 4020.

Upon initial set-up of a lighting network, a user will create a profile.Profile refers to a combination of unique username and password thatwould be related to one or many user's accounts. The profile would havemultiple purposes—1) to provide an authentication method forcommunication within the wireless lighting system (network of II Devicesand wireless devices), 2) to associate and save user preferences andconfigured settings of the wireless lighting system to the deviceapplication and possibly saved elsewhere, and 3) provide a userassociated account for billing, support, or other services. Through theinitial set-up process, as described in FIG. 39, each II Device within alighting control system will store the Profile's username and passwordor some encrypted version of the profile's username/password in itsmemory. Similarly, the wireless device and device application will storeall II Device ID's within the lighting control system (lighting network)to the device application memory.

Now referring to FIG. 41, a flow chart of a profile authenticationprocess in accordance with one embodiment of the present invention isshown and referred to as 4100. See also FIGS. 22-26 for other relatedprocess information. The profile authentication process begins in block4102. Upon any communication from a wireless device or other II Deviceto one or many II Devices, the wireless communication will include someversion, possibly encrypted, of the associated profile 4104. Uponreceipt of a wireless communication 4106, each II Device will verify orauthenticate the command by referring to the stored profile(s) in thecommunication. If the profile from the wireless communication, recoveredfrom the II Devices memory 4114, matches that of the stored profile(s)4108, then the II Device will execute the appropriate response specifiedby the wireless communication 4110. If not, then the II Device willdisregard the communication 4112. The process ends then at block 4114.Referring now to FIG. 42, a flow chart of a process for saving settingsunder a profile in accordance with one embodiment of the presentinvention is shown and referred to as element 4200. The process beginsin block 4202. After a user has created a profile 4204, when a usercreates any number of settings or information as represented as 4206(programs, defaults, groups, scenes, favorites or other information),the settings and related information can be saved to the deviceapplication memory under the heading of the user's profile 4208. Thiswould allow for replication and/or back-up of user preferences to avoidloss of data and user convenience 4210. In addition, this would allowfor sharing, duplication, and restoration of user settings throughauthentication means by referring to the user profile 4212.

In some cases, a user could save their profile and associated settingsto a computer 4214, either through the back-up of the application toapplication management software or through some light control systemspecific back-up software. In addition, the profile information andsettings could be saved or backed up through a direct connection orthrough some wireless connection. In addition, the profile informationcould be saved to a remote data center, or in ‘the cloud’ 4216.

After a profile is saved or ‘backed-up’, a user could restore settingsand profile information to an existing or new wireless device/deviceapplication 4218. A user could share the profile information andauthentication as described in FIG. 43 and included here as block 4220.A similar process would be used for adding a new wireless device withdevice application running the same profile or duplication 4222. Notethat there may be multiple profiles assigned to one lighting controlsystem or II Device network. Similarly, the same device applicationcould host multiple user profiles. The same profile could be sharedacross multiple wireless devices. The timing and exact process of aprofile saving event 4224 might differ depending on the deviceapplication. It might happen and reoccur at automatically at given timeperiods or events, or require some input from the user to either specifyevents/times, or require a user to select a save option. Though theactual process might be ongoing, for the purposes of this description,the process ends in block 4226.

All II Devices(s) will have unique id(s). Ids will depend upon the typesof II Device embodiments: (a) there could be different types of IIDevices depending upon the application where they will be used (e.g., IIDevices made for higher light (luminosity) output and limited colorrange could be called as type 1 II Device, while II Device with onlywhite light output with controllable brightness could be called as type2 II Device. Similarly, there would be different types of II Devicesbased upon different shapes and/or sizes and/or features and/or lightoutputs in terms of colors and brightness.); (b) there could be numerouspotential ID structuring of the II Devices, but consider the below as arepresentative example:

II Device id will have following structure with “aaabbbccc”. “aaa” couldbe any number of characters defining the device as II Device. Thesecharacters will be common and at the same place in the ids of all IIDevice. “bbb” could be any number of characters defining the type of IIDevice. These characters will be common for a particular type of IIDevice, but will be different for different types of II Devices. Thesecharacters will at the same place in the id of all II Devices. “ccc”could be any number of characters and with that II Devices will get aunique id. For example, consider id “illdev001001012712”,“illdev012234010512” for two different II Devices—here, first tencharacters “II Device” in both the ids will identify the device as IIDevice. Next four characters “t001” in first id and “t012” in second ididentifies the devices as different types of II Devices. Last 9characters “001012712” in first id and “234010512” in second id combinedwith other characters defines a unique id for the two II Devices.

The wireless lighting control system, including both wireless devicesand II Devices will be able to differentiate its related commands fromother wireless communication system commands through the unique IDsprefix, such as “aaa”. Additionally, a wireless communication within thewireless lighting control system would also be associated with a profileid for authentication purposes. When a wireless device then sends acommand to an II Device it will send the command directed at thespecific ID required to execute that command. Similarly, there could bea command related to a specific ID that is embedded in a command sent toanother II Device ID, in this case the second command would communicateto send the command to the second II Device. See mesh network processesfor further information.

Profile Sharing. A user's profile including their configured settingscan be transferred in a multitude of ways from an authenticated deviceapplication/wireless device to other non-authenticated deviceapplications/wireless devices to provide authentication, share profilesettings and information, or other profile related information.Utilizing the device application, there is an option to pass onauthorization to the lighting control system (II Device network) fromone wireless device to another wireless device. Additionally, a user canshare or copy their profile (saved settings) with another wirelessdevice. The receiving wireless device would need to have some version ofthe device application on their device. There are a few differentprocesses one could take to execute profile sharing, but consider thebelow as an example:

Now referring to FIG. 43, a block diagram of a device to device profilesharing process in accordance with one embodiment of the presentinvention is shown and referred to as 4300. To execute this process, onewould open the authenticated device application on one wireless deviceas represented by 4302. Then open the device application on thereceiving or new wireless device as represented by 4304. A user wouldthen select command on the authenticated wireless device application toshare profile. Might in some cases need to select command on thenon-authenticated wireless device to receive shared profile. Theauthenticated wireless device might then be prompted to select whataspect of the settings to share, such as provide access to network,share groupings, share programming, copy full profile settings, ormirror full profile settings. Upon selection of aspects to share, thewireless devices would then connect via a wireless communication 4306(Bluetooth most likely) and begin transferring the selected information,as represented by 4308, from the authenticated wireless device to thereceiving wireless device. Upon receiving the selected information theuser should have access to whatever aspects were selected.

Referring now to FIG. 44, a flow chart of a process for adding anauthenticated profile directly through the II Device in accordance withone embodiment of the present invention is shown and referred to as4400. In this process, the authenticated profile 4402 would send awireless communication to the wireless control system (II Devicenetwork), represented by 4404, with the command to add thenon-authenticated profile 4410 to each II Device's list of authenticatedprofiles. Each II Device, represented here collectively as 4406, wouldthen execute the command and add the authenticated profile to each IIDevice's list of authenticated profiles as represented collectively by4408. Once complete, the non-authenticated profile would then beauthenticated and able to communicate and control the lighting controlsystem (II Device network), as represented by 4412. Also, consider thata user could share/transfer a profile to one other device through text.An alternate way to share profile and settings would be to select anoption through the application to send a text message to another phone.This method would be useful when both devices are not present. And thesecond device is a mobile device. The text message would include aunique URL to download the application and auto-populate the profileusername and possibly the password. In addition, consider that multipledevices could simply refer or log-in to an existing authenticatedprofile that has been saved to some accessible source. This would allowany wireless device with an associated device application to access,receive, or create and authenticate a new profile by logging in with theauthenticated profile's credentials (username password).

Now referring to FIG. 45, a flow chart of a hard reset process inaccordance with one embodiment of the present invention is shown. Theprocess begins with block 4502. A hard reset with physical button, andrestore to system will now be described. Included in the design of theII Device might be an external button that when pushed resets the IIDevice back to its original manufacturing state. This will be helpfulwhen moving II Devices from different locations or power sources, fortroubleshooting purposes, and for security purposes, especially when auser no longer has access to the application device. The physicaldescription and system composing the hard reset can be found in the ‘IIDevice’ section HHHH. The process by which the hard reset occurs will bereferred to as 4500 and is described as follows, beginning with block4502: (a) a user will physically activate the reset button on theoutside of an II Device 4504; (b) a signal will then be sent to theinternal processor of the II Device with commands to execute the hardreset program that will erase all user added memory and return to themanufactured state 4506; (c) the processor and related components of theII Device will execute the required commands of the hard reset program4508; (d) all user added memory will be erased from the II Device, notincluding factory added memory 4510; (e) the II Device will return backto the manufacturing state 4512. The process for set-up would continuewith FIG. 48. The hard reset process ends with block 4514.

Referring now to FIG. 46, a flow chart of a soft reset throughapplication in accordance with one embodiment of the present inventionis shown and referred to as 4600. Included in the device application isan option that when selected will reset an II Device or multiple IIDevices back to their original manufacturing state. This will be helpfulwhen moving II Devices from different locations or power sources, fortroubleshooting purposes, and for security purposes. The soft resetprocess begins with block 4602. Within the application device, a userwould select a setting that activates the soft resets command andprogram 4604. This setting may or may not require authentication throughentering of the users profile and password 4606. The user would thenselect specific the II Device(s) and/or groups, including the entirelighting network, with which to execute the soft reset function 4608. Auser might use the ‘color coding’ process to select individual IIDevices.

Upon selection, a wireless communication will be sent from the wirelessdevice/device application to each illuminated device selected, throughthe appropriate communication methods 4610. When each II Device receivesthe communication, the processor and related components will execute thesoft reset program and commands 4612, and all user added memory will beerased from the II Device 4614. Each II Device will return to themanufacturing state 4616. The process for set-up would continue withFIG. 48. The soft reset process ends with block 4618.

Now referring to FIG. 47, a flow chart of a process for adding a new IIDevice into an existing II Device network in accordance with oneembodiment of the present invention is shown and referred to as 4700.This is the process by which a user can easily introduce into the IIDevice network.

Introducing a new II Device to an existing II Device network follows asimilar process as first setting up an II Device for the first time.Process is similar to quick set-up and easy room set-up processes. Thereare many potential processes to adding an II Device(s) to an existingnetwork, here is one example. The process begins with block 4702. Theintended II Device(s) will be in a manufacturing default, either comingfrom initial purchase or through a reset process 4704. A user willconnect the II Device(s) to a power source (most likely by screwing inand turning on a light switch, and the II Device(s) will receive powerand enter the power restoration mode 4706. Upon receiving power the IIDevice(s) will enter II Device(s) will be prone to discovery by thedevice application run on a wireless device and other II Devices withinproximity 4708. In addition, the II Device(s) will execute themanufacturing default light setting 4709. Then upon a user input on thedevice application 4710 or through a status update process where the newII Devices are found 4712, the device application will execute theprocess for adding an II Device to the application 4714. To elaborate,the status update process, as discussed in FIGS. 21 and 22, might callfor the device application to look for all II Devices in proximity. Thissearch will include identifying those II Devices that are not yetassigned to a profile, or in a manufacturing state. Next, the deviceapplication and associated wireless device establish a connection withthe II Device(s) 4716. The device application might then provide anoption for the user to confirm whether they are adding other II Devicesto the II Device network 4718. If a user selects no, it will ignore theII Device's request to pair and end the process of adding a new IIDevice to an existing network 4720. This might happen by rare chancewhen people in neighboring buildings install II Devices at the same timewithin range from each other. If a user selects yes to confirm theaddition of new II Device(s), the II Device(s) and device applicationwill follow the process outline in FIG. 39, blocks 3916—3926,collectively represented here by block 4722. This includes storing thelight ID in the device application memory and storing the profile ID inthe device application memory. Then, in place of block 3938 to moveforward with the set-up process, a user might then be prompted withother choices on how to set-up and customize the II Devices within thenetwork 4724, including adding the selection to an existing group 4726,creating a new group with new or mirrored settings for the selection4728, or creating custom settings for each II Device in the selection4730. Depending on the user's request, the appropriate set-up wouldcontinue as described in other various set-up processes, until complete4720.

FIG. 47 is also representative of a flow chart of a process forreintegration of II Device(s) back into an existing II Device network inaccordance with one embodiment of the present invention. Consideringthat the adding of the II Device(s) has proceeded through until block4716, where the device application/wireless device and II Device(s) haveestablished a connection. If the device application finds that the IIDevice ID (or multiple IDs) matches that of an II Device ID stored inthe device application 4734, then it should trigger the II Devicereintegration sub-process. If there is no match, then the process ofadding II Device(s) would continue as normal along block 4718 asdescribed previously. After finding a match to a previous II Device, thedevice application might confirm that the user would like to reintegratethe detected II Device(s) 4736. If a user selects no, then the processof adding II Device(s) would continue as normal along block 4718. If theuser selects yes, then the device application would then reassign orreconnect all stored information, profiles, defaults, and other settingsto the associated II Device(s) ID as stored in the device applicationmemory collectively represented as block 4738. This would require thedevice application/wireless device to then send a command to the IIDevice(s) to execute/store the following: (a) all related profile IDs(if stored or connected to the active profile ID); (b) all profilesettings including light default(s), active programs, and time settings.The newly connected II Device upon receipt will execute/store thecommands and respond to confirm receipt. The device application willsimilarly update its memory with the re-inclusion of the II Device(s),and they will then be re-integrated into the II Device network with allpreviously stored settings in the device application, and the processwill end in block 4720.

Now referring to FIG. 49, a block diagram of a color codingidentification process in accordance with one embodiment of the presentinvention is shown and referred to as 4900. It might be difficult for auser to select a specific II Device(s) for troubleshooting orconfiguration, especially as the number of II Devices within a networkincreases. To improve the process of selecting specific II Device(s),described here is a method to temporarily change the color of II Devicesin the II Device network and similarly provide a display of different IIDevices on the device application that mimic the same colors of theirrepresentative II Devices. This process might be executed in relation toa number of different activities or processes. We'll assume forsimplicity sake that any potential processes could trigger the processto color the II Devices and refer to such an event as ‘color codingprocess trigger’.

Upon a color coding process trigger, the device application would assigna different color to each of any number of selected II Devices and/orgroups. The device application/wireless device would then send awireless communication to each of the selected II Devices to execute alight control setting relating to the assigned color for that II Device.The device application as represented by 4902, would then display all ofthe selected II Devices with a representation of the light that'semitted by that particular II Device each represented as 4904-4920. Auser would then be able to visually see which II Device relates to theII Device representations in the device application and easily selectthe intended II Device(s). For example, the II Device represented by4904 would be colored red in some fashion, and the actual correspondingII Device would emit the same red color.

Referring now to FIGS. 50-52, various diagrams of sorting screens basedon various criterions in accordance with one embodiment of the presentinvention are shown. For certain screens within the device application,it would be beneficial to sort the list of II Devices and/or groups insome fashion that would be relevant to the user. Disclosed here are somebasic sorting methods with which to sort certain lists found withinscreens of the device application.

As shown in FIG. 50 and represented by 5000, it would often be the casethat a user would want to command or control II Devices in closerphysical proximity than those in further proximity to the user. Tosupport this scenario, certain lists 5006 in the device application 5002could be sorted by signal strength with stronger signals displayed firstin the device application, represented as example by 5004. This couldrelate to lists of: (a) II Devices—sorted based on individual signalstrength; (b) Groups—sorted based on average signal strength of relatedII Devices; (c) Programs/scenes—sorted based on average signal strengthof related II Devices. The figure represents a list of groups sorted bysignal strength, with each group and its associated signal strengthrepresented by 5008-5016.

As shown in FIG. 51 and represented by 5100, it would often be the casethat a user would want to command or control II Devices that arecurrently executing some command. To support this scenario, certainlists 5106 in the device application 5102 could be sorted by theiractive status with items that are on displayed first, represented asexample by 5104. This could relate to lists of: (a) II Devices—IIDevices that are on displayed first; (b) Groups—Groups that are ondisplayed first; (c) Programs/scenes—Programs/scenes that are activedisplayed first. The figure represents a list of groups sorted by activestatus, with each group and its associated signal strength representedby 5108-5116.

As shown in FIG. 52 and represented by 5200, considering that at timesall II Devices might not be available because their power source isturned off (light switch) or they are out of range, it might bebeneficial to sort/filter certain lists of items 5206 in the deviceapplication 5202 based on received statuses so that only those IIDevices for which statuses are received by the wireless device aredisplayed or displayed first, represented as example by 5204. This wouldrelate mostly to II Devices and groups, but possibly to programs andscenes where the un-addressable II Devices number is large. The figurerepresents a list of groups sorted by addressable status, with eachgroup and its associated signal strength represented by 5208-5216.

It would often be the case that a user would want to sort or filteritems in the device application based on some personal preferences orsettings. This might be flexible and configurable, or permanent,depending on the application. Note that different sorting methods couldbe combined in different ways, so as to first sort by one method andthen another. This would vary depending on the specific screen in thedevice application.

Now referring to FIG. 53, a flow chart of an automation programmingprocess in accordance with one embodiment of the present invention isshown and referred to as 5300. Automation refers to the program to beactivated at user specified conditions pertaining to day(s) of the week,times, and/or dates. The process begins with block 5302. A user willselect an option in the device application to create a program,specifically here an automation program 5304. The user will select anycombination and number of II Device(s) or group(s) 5306. The user willthen select the intended light setting or program to be executed basedon the automation condition 5308. This might originate from new usercustomization 5310, existing saved user favorites and defaults 5312, oras a suggested setting or program 5314. The intended light setting mightbe a single action or more of a program in itself as multiple actionsrun successively. For example, a simple automation program would turnthe II Device(s) on to a specific setting and color at a defined time.Alternately, another automation program would be to turn II Device(s) onand off successively. The user will then select a specific day(s) of theweek, date, and/or time to execute the setting and/or program 5316. Therequest could be a single event or repeating event selected by the user.For example, start on date/time, stop on date/time. Or, run every thirdMonday of the month, etc. A user would have the option to save theautomation program 5318 and/or execute the automation program at thattime 5320. If the user saves the automation program, it can be re-run atanother time by following the process described in FIG. 29. If the userchooses to execute the newly created automation program, the deviceapplication/wireless device in coordination with the respective IIDevices will execute the command as described in FIG. 29 as if theprogram was activated as beginning with block 2908. After both cases thecreation process would conclude as represented by 5322.

Similar to all programs, the user can toggle automation programs on/offvia the device application. When the program is off, the II Device(s)will not store the command in memory. When the automation program istoggled on in the future, the command will be resent to the appropriateII Devices. In the case that conflicting programs are active with theuser requested II Device(s) and time, the device application mightnotify the user and ask for the user to select which program they wouldlike to keep active. Alternately, the II Device(s) will internally havea priority level assigned to different profiles and/or types ofrequests.

An alarm timer relates to a program process by which at a certain userdesignated time or lapse of time, an action would occur in any number ofII Devices or group of II Devices. The alarm timer processes are similarto those described for general programs and automation programs.

Through the device application a user would select the program to runthe alarm or timer and select the II Devices and/or groups to executethe program. An alarm selection signifies that at a certain selectedtime, the selected II Devices and/or groups would execute an alarmcommand to adjust lighting to the user's requested command. Therequested command might be of a dynamic nature or a program in itself soas an execution of multiple commands in sequence such as a flashing orchanging of color or brightness. When an alarm program is selected, thedevice application would interpret the time requested by the user andsend a command to the lights and/or groups selected to execute thecommand or series of commands at that specified time. Each II Devicewould receive the commands through the wireless communication, interpretthe commands by the processor, and then store the request in memory tobe executed at a later time. Inside each II Device, the processor wouldmonitor the internal real time clock and look for a match in the clock'stime to the alarm program request stored in memory. If it matches, thenthe processor would execute the alarm command(s).

A timer selection signifies that after a certain amount of time passes,an II Device or combination of II Devices would act in some predefinedmanor. The user would first select the II Device(s) and/or group(s), ormultiple to run the program. Then the user selects the amount of time inminutes, hrs., etc. via their application. Once selected then the devicerunning the application will send a wireless signal to the designated IIDevice(s) with the specific amount of time to count down from. At thepoint when all the II Device(s) confirm receipt of the timer request tothe device's application, the timer will begin in unison with all IIDevice(s) applicable. Each II Device will then countdown using internalreal time clock, processor, and other embedded components. If multipleII Devices, they will count down individually, but all in unison. Whenthe timer reaches zero, the II Device(s) will execute the commandrequested by the user. A user can request to repeat any timer programsto count down and then repeat. The application interface might alsopresent a timer display showing the amount of time counting down. Uponreaching zero, the application might also present some other actionswithin the application. This time down feature might also be valued forgaming scenarios using the II Devices as signals.

Referring now to FIG. 54, a flow chart of a music sync process inaccordance with one embodiment of the present invention is shown andreferred to as 5400. This is a type of program specifically forautomatically synchronizing the II Device(s) to music played on the sameenabled device. The process begins with block 5402. Through the deviceapplication or through a specialty device application, the user willaccess the music sync program 5404. The user would then select the IIDevice(s) with which to sync the music 5406. The user will then selectthe type of II Device arrangement and the light setting theme 5408.Options for selection could depend on a number of different factors,such as the number of II Devices selected 5410, the proximity of theselected II Devices 5412, suggested options 5414, user history or savedpreferences 5416, or completely new customized configurations 5418. Forexample considering the arrangement, if the number of II Devices is 1,then the device application will only sync to a mono type interpretationof the audio. If number of II Devices is 2 or more, then the deviceapplication will evenly distribute and assign each II Device to eitherof the 2 primary (L, R) stereo channels within the music file. Thedevice application will visibly show each II Device and to which channel(L, R) the II Device is assigned to.

Further considering arrangement, if a music file is able to carrymultiple channels or if the music file can be broken into multiplechannels based on frequency, pitch, or other aspects of sound, an IIDevice could similarly be assigned or distributed across multiple IIDevices. Similarly, considering selection of the light theme, the deviceapplication might display potential lighting themes options for the userto select or the user can customize their own preferences. Here, theremight be default settings that have a color and/or brightness themeassociated with each channel. The settings will be variations of coloror themes of color assigned to each channel. For example, one mightinclude all colors available randomly assigned to each II Device.Another option might allow for the channel colors to change over time.Another option might suggest only red hued colors, or any other type ofcolor hue. Once an arrangement and lighting theme is selected, the userwill be able to see and verify the selection 5420. At any time, the userwill be able to reconfigure the arrangement or light themes, 5422, suchas to move or reassign lights to different channels, select between monoor stereo lighting modes, or choose a different theme. Once theconfiguration is selected, the application device will notify theselected II Devices of the command and ensure all II Devices are readyand addressable 5424. This will be done via the appropriatecommunication and control processes. The user would then select musicfile(s) stored on the device (or streaming music) to be played 5426. Asthe music is played through the device application, the deviceapplication will interpret the music file wavelengths to send continuingcommands to each II Device previously selected to turn on and off,adjust brightness, and change colors depending on the music constructwithin that channel at that time and the selected arrangement and theme.

Possibilities for interpreting the music construct is as follows: Foreach music channel in the music file (L,R), when there some output ofsound to be played or amplitude in the music, that would correlate withthe light(s) assigned to that channel to turn on (to emit light). Forexample, if a bass drum is played in the left channel, the audible soundwould coordinate to the visible light from that assigned left channel'sII Device(s). For each channel (as previously assigned), the brightnessof the light emitted by each II Device could brighten or dim dependenton the respective increase or decrease in amplitude of the music withinthat channels music file. Such as that louder sounds would coordinatewith brighter lights and vice-versa. Respective amplitude would be thedependent variable, not true amplitude. Additionally, different pitchranges might correlate with different color combinations of lightoutput. Additionally, the bpm (beats per minute) might be interpreted sothat after a standard measure of bars (time of playing) the color orchannel assignment of the II Devices might change.

A user could also adjust the overall brightness maximum output to theirpreference through the device application, similarly referred to in thefigure as 5422. This information would be taken into context beforerelaying commands through to the II Devices. The application devicewould automatically or through user input manage and match the output ofaudio to the output of lighting commands and delay the audio output toany delay in communication to the II Devices so as the actual soundheard through a speaker would match the same time that the lightilluminated from the II Device(s) 5428. The application would continueto run on the device while continuing to interpret/translate the musicand channels played into commands to be executed by the assigned IIDevice(s). When the music sync program application is stopped or exited5430, the assigned II Devices would revert back to their previousprogrammed state if applicable or default level 5432. The music syncprogram/application would complete 5434.

A predefined program so a user can set their II Devices to slowly turnon with certain color displays at specific times to simulate the effectof a sunrise. In many parts of the world, people have to get up beforethe sun, this process allows for a user to select their II Devices toturn on slowly, mimicking a sunrise, before their alarm or at a certaintime to help wake them up. Setting up the program through the deviceapplication, a user could select the special program through thepredefined program list or through the groups menu. The sunrise programwould be a suggested program for those groups containing the word‘bedroom’. The user would be able to adjust the length and type ofsunrise if they choose. Type relates to variations in color schemes. Theuser will be asked to enter a time for the sunrise program to execute,or to create an alarm with the sunrise. If the alarm program is alsoset, the two could be run simultaneously or within one program. Once setand accepted, the application device will communicate the automationprogram request to the selected light(s). The light(s) will receive theautomation program request and store the program in memory to beexecuted upon the requested time. The program settings could be savedfor future use or set to run at any frequency similar to any automationprogram.

Executing the program. When the sunrise program is active, the programwill be executed similar to any other automation or alarm program. Thesuggested colors used in the sunrise program will most likely includeorange and red colors that would brighten over time until fully lit whenthe alarm or timer condition is met. Blue LEDs might also be included toprovide the short wavelength light mimicking that of the sun.

In some embodiments, a light will be connected or equipped with anambient light sensor that can detect the light levels present within anarea, relay that information to the II Device's controller, which couldbe interpreted as a program input resulting in a change in the lightingbrightness and/or color. Various programs are possible to utilize the IIDevice sensor's information as an input to causing some output in termsof a change in the brightness and/or color of one or more II Devices. Inone program example, a user will select a preferred light level for IIDevice(s) or group(s) through the device application. Each II Device canhave a different setting, giving the user to select any number of uniquecombinations. Selecting the preferred level might also be done throughthe user defined defaults for each II Device. When selected, the deviceapplication will then send a request through the controlling device toeach II Device that the user has selected through the program, askingfor each II Device's related ambient light sensor information. Thedevice application upon receiving the light sensor information willstore the default settings in the application or device's memoryrelative to each II Device. Alternatively, the II Device itself willrecord the sensor information in its own memory. The user can then atany other time activate an automatic adjustment program. Uponactivation, the device application will send a communication to each IIDevice associated with the program. The communication will instruct eachII Device to compare the current II Device sensor information againstthat associated with the preferred lighting level. This informationwould either stored in the II Device's memory or relayed via the deviceapplication's communication.

The II Device would then adjust its brightness and/or color depending onthe light sensor data's relationship between the current and preferredlighting level. Simplified, if the current light sensor showed lessluminosity than the preferred level, then the II Device would increaseits own brightness. Alternately, if the current light sensor showed moreluminosity than the preferred level, then the II Device would decreaseits own brightness. The relationship between the difference in currentand preferred light received will not be an equal or absoluterelationship to the change in the brightness of the light.Alternatively, it will be some functional relationship dependent on theabsolute and respective levels of light. The program and/or II Devicesthemselves would repeat this process for the duration that the programis active.

Now referring to FIG. 58, a block diagram of a LED driver scheme inaccordance with one embodiment of the present invention is shown.Various LEDs arms (302, 304, 306 and 308) are driven by the LED drivers(318, 320, 322 and 324) as shown. The LEDs drivers turn ON or OFF basedon the ON or OFF signal provided by the microcontroller/processor 106 asshown. When LED driver is ON, current passes through its LEDs arm, andLEDs in that arm produces light. LEDs arms (LEDs1 302, LEDs2 304, LEDs3306, and LEDs4 308) can have different types of LEDs including differentcolors and different electronic ratings. Each LEDs arm may have one ormultiple LEDs in a series or parallel or combinations of those. With thedriver scheme as per FIG. 58, color mixing can be achieved bycontrolling the signals to the LED Drivers (Sig1 5826, Sig2 5828, Sig35830 and Sig4 5832) which in turn control the ON/OFF times of the LEDdrivers individually i.e. by toggling the pins individually to ON or OFFstates at a frequency that could be above 85 Hz. To limit the sum of thecurrents going through different LED drivers at a time, one could makesure not to have multiple pins controlling signals Sig1 5826, Sig2 5828,Sig3 5830 and Sig4 5832) of the LED drivers ON at a time. This could beachieved by a program running in the processor that controls the pins'ON/OFF states. In this way one need not have a PWM control of the LEDsdrivers, which also helps to optimize the frequency required to run theLED drivers taking into the consideration their maximum and minimumfrequency of operation and flickering issues associated with the LEDsbeing driven by their respective drivers.

An example of how this circuitry and program controlling the pins workwill now be described with a specific case having these assumptions: (1)The high level (ON) signal if passing through each of the Pins, Pin1,Pin2, Pin3 and Pin4 in FIG. 58 passes at every 10 ms of a time period;(2) The ON signals through each of the pins are not overlapping; (3) LEDdrivers are designed for 1 A output current, i.e. when any Pin is sethigh (ON), it makes the respective driver ON allowing up to 1 A currentpass through its LED arm; (4) The user wants a yellow light output atthe maximum luminosity possible, for which LEDs1 302 and LEDs2 304should be illuminated equally by sending same amount of average currentthrough them; (5) LEDs1 302, LEDs2 304, LEDs3 306, and LEDs4 308 armshave multiple RED, Green, Blue and White LEDs in series respectively;(6) For full luminosity of yellow light that can be produced throughthis scheme, the average current passing through RED LEDs and Green LEDsshould be half the maximum average current possible through them, whichcan be achieved by turning LEDs drivers ON/OFF as per the timing diagramin FIG. 60A. For 40% of the maximum luminosity of yellow light, RED LEDsshould be ON for 20% time and Green LEDs should be ON for 20% time asshown with the signals SIG1 and SIG2 in FIG. 60B. Similarly, to producea type of orange light consisting of 40% of Red, 20% Green and 10% ofWhite could be achieved as per FIG. 61.

The 10 ms time period in the timing diagrams in FIGS. 60A, 60B and 61are divided based on the count set into the controller/processor, whichmay come from another device communicating through various means such asSmartphone, computer, etc. connected through wires or wirelessly.Consider that the 10 ms time period is just an example. Referring toFIG. 59, this time period can vary based on the counts for respectiveLEDs with which the ON or OFF times for a particular LED signal arecalculated. For example, consider that the RGB or equivalent counts tocontrol the II Device are such that the Red is required to be ON for 20%of the overall time, Green is required to be ON for 30% of time andWhite required to be ON for 50%. Here Red (SIG1) turns ON for 2 ms andthen turns OFF; as soon as Red turns OFF Green (SIG2) turns ON for 3 msand then turns OFF; and as soon as Green turns OFF, White (SIG4) turnsON for 5 ms and then turns OFF and this cycle repeats. Here the totalON/OFF time cycle for any LED is 10 ms. Now consider a second scenario,where the RGB or equivalent counts are such that the Red is required tobe ON for 50% and Green is required to be ON for 50%. Here Red (SIG1)turns ON for 2 ms then turns OFF; as soon as Red turns OFF, Green (SIG2)will turn ON for 2 ms and then turns OFF and cycle repeats. Here thetotal ON/OFF cycle time for LED is 4 ms which is different than theprevious scenario. In addition, consider a third scenario where Red isrequired to be ON for 25% and Green is required to be ON for 25%. HereRed (SIG1) turns ON for 1 ms then turns OFF; as soon as Red turns OFF,Green (SIG2) will turn ON after 1 ms for ams and then turns OFF andcycle repeats. In this scenario the time cycle is still 4 ms, but thetotal time Red and Green are ON is 50% as compared to previous scenariogiving 50% less brightness out of the Red and White LEDs in the sametime cycle of 4 ms. Having flexibility in the time cycle as fordifferent color and/or brightness combinations helps in reducing theoverheads for the processor in calculating the cycle time and ON and OFFtimes for each LED. To further explain with an example, consider thatthe Red, Green, Blue and White counts for a particular color are Redequal to 255, Green equal to 127 and Blue and White equal to 0. Alsoconsider that the processor's 106 internal clock generates the overalltime period and triggers ON and OFF signals for LEDs. In this situation,the processor can count down from 255 to 0 (or count-up from 0 to 255)forming a time period, let's assume that turns out to be 2.55 ms forwhich Red (SIG1) will be ON. While immediately after Red turns OFF,Green (SIG2) will be triggered with the turn ON signal and will remainON until the countdown is from 127 to 0 which making Green turned ON for1.27 ms. Similarly, if the counts are 255 for RED, 100 for Green and 200for Blue LED, the countdown for each of these LEDs will directlygenerate the time cycle where Red (SIG1) is now ON for 2.55 ms then OFFturning Green (SIG2) immediately ON for 1.00 ms and when Green (SIG2)turns OFF after 1.00 ms, Blue (SIG3) turns ON for 2.00 ms and then TurnsOFF immediately turning ON Red (SIG1) and repeating the cycle. In thesetwo scenarios as explained, the ON/OFF time cycle for LED is 3.82 ms(2.55 ms+1.27 ms) for first scenario, while ON/OFF time cycle is for LEDin second situation is 5.55 ms (2.55 ms+1.00 ms+2.00 ms). In thesescenarios the 100 counts countdown is equivalent to 1.00 ms, howeverthen it could be different depending upon the processor 106 type, clockit is running ON, the clock division/multiplication being taken placeinside the processor 106 and division/multiplication defined for Red,Green, Blue and White counts to ensure they are proportional to eachother. For example, even if in one scenario the count for Red is 255,for Green is 100 and for Blue and White is 0, the processor may multiplyor divide the count by certain number such as multiply 2 making them510, 200, 0 and 0 for Red Green, Blue and White respectively to addressany limitations of the LED driver's minimum turn ON and OFF timerequirements and to ensure minimum cycle requirement for maintaining thepersistence of vision requirement (which many times considered asminimum of 85 Hz cycle). This way the overheads of complex calculationsfor calculating the time cycle, ON/OFF time for each LED are minimizedsaving processor's 106 processing power for other required calculationsand giving better response. In addition, there is no need of usingcomplex PWM (Pulse Width Modulation) of the signal and calculationsrequired to calculate parameters of PWM every time to control the lightoutput. With this configuration a processor that is cost effective andhas low processing power can be used.

In FIG. 59, the process is explained in general. Controller/processor106 receives counts corresponding to at least one LED output in Block5900. The controller/processor 106 multiplies or divides the count ifand when required considering the ON/OFF trigger cycle that is dependenton processors internal clock cycle and persistence of vision requirementin block 5902. After the counts for LEDs are calculated, in block 5904,the controller/processor 106 turns the signal ON by toggling the signalpin to logic 1 for first color LED out of given N LEDs and starts thecountdown from respective calculated LED count to 0 and then turns thesignal OFF by toggling the signal pin to logic 0. In block 5906,controller/processor 106 waits with next countdown when all LEDs aresupposed to be OFF depending upon the brightness level requirement. Thecountdown could be as low as 0. For example, the LED counts calculatedfor full intensity of color with Red, Blue, Green and White are 252,100, 0 and 0 respectively, then the counts for Blue, Green and White for75% intensity would be 189, 75, 0 and 0. For full intensity the Redsignal will become high i.e. Red LED ON for countdown from 254 to 0 andthen it will become low i.e. Red LED OFF. Immediately after that theGreen signal will become high i.e. Green LED ON for countdown from 100to 0 then it will turn OFF. As Blue and White counts are 0, they willnot Turn ON but remain OFF. Thereafter, the cycle with RED turning ONimmediately continues. However, for 50% intensity, the Red signal willturn high i.e. Red LED ON for countdown from 189 to 0 and then it willturn OFF and will remain OFF for countdown from 63 (calculated as252-189) to 0. Immediately after that Green will turn ON for countdownfrom 75 to 0 and then it will turn OFF and will remain OFF for countdownfrom 25 (calculated as 100-75) to 0. With Blue and White counts 0, Blueand White LED will always remain OFF. The cycle repeats until new countsare available. This countdown method could be different, however, itwill be intended to keep percentage of Signal of a particular LED ON outof entire time cycle same as calculated in above example. Blocks 5904,5906, 5908 and 5910 explain the process in general. The cycle repeatsuntil the new counts for LEDs for new color and brightness combinationare provided or calculated as shown in general in blocks 5912 and 5914.

With such control of LED drivers (318, 320, 322 and 324) which includenon-overlapping ON signals for two or more LED drivers, one gets theability to get the brightest light possible from the LEDs in respectivearm in the scheme with the limited power available from the powersupply. One is able to design the LED drivers for the maximum possiblecurrent possible through LED arm irrespective of how many additional LEDarms are required from the given power supply. For example, one can keepone LED driver ON continuously and pass maximum current possible throughits LED arm and get highest possible output. Similarly, if one couldpass ON signal for first half of the cycle through one LED arm bykeeping its LED driver ON for that time and ON signal for the secondhalf of the cycle through other LED arm getting maximum light output forthe color formed by mixing the lights from the LED arms in theproportion of their ON times.

This also allows optimizing the frequency of the ON/OFF signal to LEDdrivers reducing the dependency upon limitation of the time required fordrivers to change their state, i.e. from ON to OFF and vice versa ascompared to the sequential non-overlapping PWM signals. It also reducesthe overhead on the controller/processor as it need not create manynumbers of PWM signals for controlling various drivers which in turncontrols current through respective LED arms of LEDs. It is nowachievable by toggling the pins from high (ON) state to low (OFF) stateonly. In addition, the controller can be programmed to keep OFF timebetween the two non-overlapping ON signals as shown in FIG. 61. Thishelps drivers to start earlier making sure that the current through itreaches to the required peak level i.e. turns ON fully by the time it issupposed to do so.

FIG. 62 is a block diagram of a lighting system in accordance with oneembodiment of the present invention. II Device 140 or 6202 may havevarious defaults such as: (1) Manufacturing Default, which could be thebasic light setting executed when one resets the controller/processor106 of II Device 140 or 6202; (2) Active Light Default, the activedefault light setting that could be executed when the II Device 140 or6202 is turned ON; and (3) many Passive Light Defaults, the lightsettings those could be executed when specific triggers are provided tothe controller/processor 106. These defaults could be stored in itsinternal memory or memory on board 108 or memory of an externalperipherals or controlling devices such as remote controlling device6204 with which II Device 140 or 6202 is communicating.

All these defaults could be executed with various ON/OFF cycles providedby an external electronic switch controlling the power of the II Device6202 such as wall switch 6200 in this case. For example, theManufacturing Default could be executed when the wall switch 6200associated with the II Device 6202 is turned ON and OFF two times in aspecific time period such as four seconds. A particular Passive LightDefault could be achieved by turning II Device 62020N and OFF four timesin five seconds through a light switch 6200. Similarly, other lightdefaults can be executed with other switch ON/OFF combination cycles.The ON/OFF combinations here are type of a trigger for the II Device 140or 6202, and various such combinations form different triggers. Thesetriggers through a switch are particular ON and OFF times those arestored during the process by controller/processor 106 in its internalmemory or memory on board 108 or memory of an external peripherals orcontrolling devices such as that of a remote controlling device 6204with which II Device 14 or 6202 is communicating wirelessly. Then thesestored ON/OFF times are compared to check if any defined trigger in thesimilar memory has been generated, based on which II Device 140 or 6202execute particular light default or light settings.

One way to achieve this is by defining various ON/OFF times definingtriggers into the II Device's memory 108. When II Devices 140 or 6202 isswitched ON/OFF at a particular cycle, this cycle is stored and comparedby the controller/processor 104 or remote controlling device 6204 toexecute the required default. The II Device's RTC 110 or clock of remotecontrolling device 6204 could be used to monitor and store the ON/OFFswitching times the into a specific memory.

In addition, the user can provide triggers not only though a switchcontrolling power to II Devices, but other external devices connectedthrough wire(s) electrically or wirelessly to the II Device 140 or 6202.Furthermore, Light Defaults could be a specific light setting with aspecific color and brightness or a light program that changes the lightoutput as a function of time or other events.

Referring FIG. 63, II Device 6306 could be controlled through remotecontrolling device 6300 that has at least one or combination of built insensor(s) in following categories:

-   -   Motion and navigation sensors including but not limited to        accelerometer, gyroscopic, proximity sensor, digital compass,        Global Positioning System Sensor;    -   Acoustic, sound and vibration sensors including but not limited        to microphone, Lace sensor (guitar sensor), etc.;    -   Automotive and transportation sensors including but not limited        to speedometer, speed sensor, torque sensor, etc.;    -   Chemical Sensors including but not limited to Smoke detector,        Breathalyzer, Electronic Nose, Potentiometric sensor;    -   Electric and Magnetic sensors including but not limited to        current sensor, electroscope, magnetometer, metal detector,        voltage detector, etc.;    -   Environment, weather, moisture, humidity sensors including but        not limited to dew sensor, rain gauge, rain sensor snow gauge,        humidity sensor, humistor, gas detector, leaf sensor, etc.;    -   Flow and fluid velocity sensors including but not limited to air        flow meter, water meter, Anemometer, flow sensor, gas meter,        etc.;    -   Position, angle, displacement, distance, speed, acceleration        sensors including but not limited to tachometer, accelerometer,        rate sensor, etc.;    -   Optical, light, imaging, photon including but not limited to        flame detector, ambient light sensor, photo resistor,        phototransistor, infra-red sensor, fiber optic sensor,        photodiodes, etc.;    -   Force, density, level sensors including but not limited to force        gauge, load cell, piezoelectric sensor, strain gauge, etc.;    -   Thermal, heat, temperature sensors including but not limited to        temperature gauge, thermometer, thermistor, thermocouple,        infrared thermometer, etc.;    -   Presence sensors including but not limited to occupancy sensor,        touch switch, motion detector, etc.; and    -   Pressure sensors including but not limited to barometer,        piezometer, pressure gauge, etc.

Referring FIG. 63, the above mentioned sensor could be a part of aremote controlling device 6300 capable of communicating with andcontrolling the II Device(s) 6304. In addition, referring to FIG. 64,above mentioned sensors could be a part of other peripheral device 6400that could communicate with II Device(s) 6304 through other intermediateremote controlling device(s) 6406. In the FIG. 63, an example is shownwhere a remote controlling device 6300 with motion sensor oraccelerometer is shaken or moved or rotated in a particular direction atleast once to produce a predefined signal that in turn makes remotecontrolling device to send a command or data to the II Device 6304 toexecute a particular light setting or function. Similarly, in FIG. 64,device with sensor 6400 sends command or data for such predefined signalto II Device 6404 directly or through intermediate remote controllingdevice 6406 to execute a particular light setting or function.

The II Device system will have a specific Software Development Kit (SDK)and/or Application Program Interface (API) for developer(s) to buildvarious programs and features for the II Devices(s). Referring to FIG.65, II Device will contain unique functions which could be used by asoftware/application developer to implement different applications orfeature. For example, the functions may include:

-   -   a) Functions for connecting and disconnecting remote controlling        device(s) to II Devices(s) 140 individually or in group. The        function includes the protocol to connect to the lighting device        where lighting device's identification number is integral part        of it.    -   b) Functions 6512 to send commands to II Devices(s) 140 to        change the color and brightness, the command will consist of        values proportional to the luminosity output of each LED arms        driven by LEDs current controlling circuitry 120. These values        will be read and decoded by controller/processor 106 and it will        control the flow of average current through LEDs accordingly to        illuminate LEDs to desired level of brightness. One of the        functions will include values for defining the color and the        brightness in terms of Red (R), Green (G), and Blue (B) values        ranging from 0 to 255 representing standard RGB color space.        Another function will include values of Cx and Cy ranging from 0        to 1 representing standard CIE color space.    -   c) Functions 6510 to send command to II Device(s) 140 to set        date and time of RTC (Real Time Clock) 110 or read date and time        values from RTC which can be used to automate the lighting        output such as to turn ON/OFF at a particular color and        brightness at a particular day and time.    -   d) Function 6508 to send command to read and write        controller/processor's 106 memory or the other on board memory        108 of the II Device(s) 140.    -   e) Functions 6514 and 6516 to send commands to access the        controller/process or programs such as reading sensor data such        as that of ambient light sensor 118 or any other internal or        external.    -   f) Functions 6518 to communicate with external wireless devices        such as Remote controlling Device(s) through II Device's 140.

Referring to FIG. 66, depending on location and proximity, the wirelesssignal strength between an II Device 140 and a controlling device canvary. In addition any impediments, such as a wall, can also have aneffect reducing the wireless signal strength between an II Device(s)140, (6600, 6602, 6606 and 6604) and a Remote Wireless Device 6608capable of communicating with II Device(s) 140 (6600, 6602, 6606 and6604). The remote wireless device 6608 and II Device(s) 140 (6600, 6602,6606 and 6604) can then be put in a state where when signal strengthsare detected beyond a certain threshold then the II Device 140 shouldexecute a command.

The exact threshold and the command could be user adjusted or preset. Inthis scenario, a user with the remote wireless device 6608 which couldbe remote controlling device for II Device(s) 140 (6600, 6602, 6606 and6604) could move around an area where the II Device(s) are stationary,and while moving around the signal strengths would vary and only thoseII Device(s) with a signal strength above the certain threshold would beactivated. Similarly, when the remote wireless device 6608 continues tomove and the signal strength diminishes past the threshold then the IIDevice(s) 140 (6600, 6602, 6606 and 6604) can have a separate commandsuch as turning off.

The II Device(s) 140 (6600, 6602, 6606 and 6604) and the remote wirelessdevice 6608 might be set by a user in a state to monitor signal strengthand thus execute the proximity program. It might also be scheduled by auser to be executed at set times. In some scenarios the controllingdevice will search for II Devices, assess their signal strength, andsend commands to the II Devices that have signal strengths above thethreshold. In other scenarios, the II Devices will search for the remotewireless or controlling device to come into direct range, assess thesignal strength, and take action accordingly. Or it can be somecombination of the two. The search between the II Devices and the remotewireless or controlling device can be continuous or intermittent at somedefined time, e.g., every second.

In some cases, variations or some effect on signal strength can beinterpreted as some barrier, such as a wall 6610, between the II Device6606 and the remote wireless or controlling device 6608. If the signalstrength is interpreted as having a barrier, such as a wall, between theII Device and the controlling device, then the command to turn on mightbe disregarded even if the signal strength is above the threshold foractivation. In addition, the controlling device or II Devices might haveinformation related to the general layout of the II Devices and barriersin between. This can come from user generated information, historicaluse patterns, or II Devices relative signal strengths from each other.The remote wireless or controlling device might use this information tosimilarly make assumptions on whether an II Device is intended to becontrolled within proximity. For example, assume II Device 1 and 2 arein room A, and II Device 3 and 4 are within room B. If in Room A thenthe true signal strength for II Device 1 and 2 would be beyond theproximity threshold, but consider II Device 3 is also beyond theproximity threshold but II Device 4 is not beyond the proximitythreshold. Here, the controlling device could interpret this as the userbeing in room A and only send a proximity command to II Device 1 and 2,ignoring II Device 3.

Various application interfaces will now be described. On the controllingdevice for II Device 140 the user interface for the application can bemade to be intuitive and representative of the lighting environment.There are multiple potential facets that could be combined to create anintuitive user interface not limited to a real-time representation ofsome or all lights, their status, and any active programs.

Referring to FIG. 67, in terms of representation, the II Devices 140 canbe set-up in a representation 6700 similar to that of an overhead viewof the space in which the II Devices are installed (i.e., a visual orvirtual representation). In this case there can be a user led orautomated process to place II Devices in respective locations on thescreen. In addition, there might be a user generated or automatedprocess where a user set's up their II Devices within the framework ofrooms such as living room 6702 in the figure. Here a user would beprompted to create an approximate representation of the walls of a roomthen drag or input where the II Devices are related to the room layout6702. The creation of the walls can be done in multiple ways usingdirect user input (dragging, using corners, or using predefined shapes)as well as camera functionality and estimation tools. Once a room isdefined and II Devices within a room are defined a user can select theroom as a whole or drill into individual lights within the room.

Further, a user can add II Devices to an existing room or create newrooms as representations and add other II Devices into that room. Heremultiple rooms could be joined together to create a full overhead layoutwith walls or spaces in between as per representation 6700 in thefigure. Multiple rooms can be joined together to create differentfloors, so that a user can select between overhead representations ofdifferent floors. Further, multiple II Devices can be combined togetherto create smaller clusters or groups of II Devices. Here the clusterwould be editable but treated at the layer in the general user interfaceas one II Device.

This provides a scalable user interface depending on the number of IIDevices and the number of rooms configured by the user, but alsoprovides an easy representation of all lights at any time. A user canselect a whole house, a floor, a room, or individual lights within theselection area by zooming in or zooming out. In addition, a user canselect any combination of floors, rooms, or lights to select or create aquick grouping at any time. The overhead representation would includewhether each individual II Device is on or off, the brightness, andpotentially any active or scheduled programs or lighting effects. Inaddition to working as a representation of multiple II Devices, theoverhead representation can be utilized for other intelligent devices orsensors related to the environment.

As the II Devices can represent colors as well as variations of whitewith different saturation levels, the application representation in thecontrolling device needs to have a similar representation. Referring toFIG. 68, in the application interface, this can be represented by havinga color area 6806, 6808, a white light amplitude/saturation area 6810and brightness area 6812. The color area could be a color wheel 6806,6808 or box representative of the available color combinations, thewhite area could be a rotating or directional level 6810. When the whitelight area is at the lowest level 6814, the color area would be fullysaturated with bright colors shown as R, G and B. When the white lightarea is at its highest level 6816, the color area would be almostcompletely white. In between, incremental increases in the white lightlevel 6820 would have an effect to add less saturation to the colorarea, looking like a white gradient overlaid on the color area 6818shown with sB, sG and sR (stands for less saturation of R, G and B).Here if multiple II Devices with differing ranges in color saturationare present, the controlling device will note this and only allow thewhite light level to reduce to the appropriate level representative ofthe less flexible II Devices range.

Any selection could also be saved by the user to a default area on thescreen for quick selection such as presets 6822 i.e. when user pressesdefined preset the selected II Device would emit the color, brightnessand saturation of the selected preset. In addition brightness could alsobe adjusted independently as a proportional amount of brightness emittedby the II Devices by controlling the brightness area 6812. All theserepresentation areas could be given different intuition, however, theconcept of controlling the color, saturation and brightness of IIDevice(s) through user interface would remain the same.

As an alternative to wireless control through a controlling device, someembodiments might rather or also have a manual hue adjustment optionwith some mechanical input, such as a button, a knob, or the like. Auser can adjust the hue, color, or brightness of the II Device. Oneexample of a button would be a rotating ring around the edge of the IIDevice that in different positions would relate to different hues orcolors. With torque a user could turn the ring to create different ringeffects. Another example would be a very low voltage conductive area onthe outside of the light that when touched would change the color orhue. Again another version might be a button or switch somewhere on theembodiment that when turned would create a different hue, brightness, orcolor.

Now referring to FIG. 69, a flow chart of scheduling programs foroperating a lighting device in accordance with one embodiment of thepresent invention is shown. The user selects II Device(s) to beprogrammed with scheduling (lighting programs, effects orconfigurations) through user interface on a remote wireless device suchas wireless controlling device or smartphone in block 6900. Forscheduling a single II Device or a group of II Devices, the user entersprogram(s) with at least one parameter such as date, time to turn IIDevice ON/OFF or change light output, brightness, saturation, color,duration of the program, number of repeats through user interface oncontrolling device in block 6902. The programs are created and stored orare already stored in at least one of the memories such as theprocessor/controller's 106 internal memory, on board memory 108, in thememory of remote wireless device 2548, or any other peripheral devicecommunicating to II Device directly through wires or wirelessly orindirectly through other intermediate devices in block 6904. In case ofmultiple programs those could conflict light outputs from the same IIDevice(s), the user can assign priorities to the programs to avoidconflicting situations for II Device(s) light output in block 6906. Theuser programs the II Device(s) and II Device(s) run the program(s) inblock 6908.

Referring now to FIG. 70, a flow chart of selecting a lighting sequenceof a lighting device in accordance with one embodiment of the presentinvention is shown. The user selects at least one II Device on whichuser wants to run the lighting sequence (lighting programs, effects orconfigurations) through a user interface on a remote wireless devicesuch as smartphone or a wireless controlling device in block 7000. Theuser sends command to run at least one lighting sequence which is storedin at least one of the memories such as the processor/controller's 106internal memory, on board memory 108, in the memory of remote wirelessdevice 2548, or any other peripheral device communicating to II Devicedirectly through wires or wirelessly or indirectly through otherintermediate devices in block 7002. In case of multiple lightingsequences those could conflict light outputs from the same II Device(s),the user can assign priorities to the lighting sequences to avoidconflicting situations for II Device(s) light output in block 7004.Thereafter, the user programs the II Device(s) and II Device(s) run theprogram(s) in block 7006.

Now referring to FIG. 71, a flow chart of storing various parameters fora lighting device in accordance with the present invention is shown. TheII Device and/or remote device stores various parameters such as the IIDevice ON and OFF schedules, color/brightness values at particular timesand for given durations, programs in at least one type of the memorybeginning in block 7100. The remote device software or the softwarestoring the data learns the pattern or behavior of the user or II Deviceusage and interprets it as a function of at least one of the parameterssuch as time of the day, date, weather, respective user, room occupancy,inputs from sensors, etc. in block 7102. With the learned pattern orbehavior the II Device or remote device automatically enacts the patternor behavior giving better user experience and improved energy efficiencyof the II Device usage in block 7104. The software keeps learning thebehavior of II Device usage and optimizing the automatic performancethereafter in block 7106.

Referring to FIG. 72, instead of a user interacting directly via touchwith the application on the controlling device, alternatively a usercould use voice commands to execute and control one or many II Devices.The user turns ON the device application for controlling II Device(s) inblock 7200, and provides voice commands to the remote controlling deviceto control II Device(s) in block 7202. Example voice commands caninclude, but are not limited to, Lights Turn ON, Lights Turn OFF, LightsDim To certain Percent, Turn ON X Lights, Lights Start Certain Program,Lights Stop certain Program, etc. The voice command can also act asgeneral setting and configurations, executing a program, executing ascene, or setting a schedule those could be default commands withfactory settings or user created commands.

The voice service could be integrated into the device application or usethe controlling device's own voice service. Popular voice commands suchas ‘Turn on X light’ could be added to the reference database. The X inthis consideration could be related to the level of control the user isselecting. For example, ‘Turn on All lights’ would turn on all IIDevices. ‘Turn on Bedroom lights’ would turn on those II Devices in theroom named ‘bedroom’. The step 7204 includes that software interpretsand recognizes the voice commands and convert those to specificelectrical signals if the commands are meant for IID(s). Another step7206 includes the remote device sending the commands to the II Device(s)and II Device(s) acting according to the commands. The commands can alsoalways start with specific word or set of words so that the softwarerecognizes the voice commands are for controlling the II Device(s) thatalso helps it ignore other unrelated voice inputs.

Forming a network of II Devices with its controlling device(s) andadding II Device(s) in the existing network of its wireless controllingdevices(s) such as Smartphone will now be described. Referring to FIG.73, the setup process may include the wireless controlling device thatis able to control the II Devices 140 in which wireless controllingdevice searches for powered II Devices 140 and adds them into itsnetwork. When a user wants to add new II Device(s) 140 to the existingnetwork, the controlling device searches for all the II Devices 140 inthe vicinity but shows only ones that are not part of the existingnetwork, and user can add these new ones to the network. User canspecifically ask device to search for new II Devices in the vicinity bygoing into the setup mode onto the device application 7302. This way itis convenient for the user to look and add only the new II Device(s) 140instead of looking at the entire list of the devices and finding theright ones to add into the network. This is achieved by comparing theidentification numbers of the existing II Devices into the network withII Devices to be added into the network 7304, 7306, 7308, 7310.

In some scenarios such entertainment stage where multiple lights arepart of the system on the stage, very precise synchronization of thelight effects may be required, i.e. no or very minimal delay in thelight output changes of various lights is required. There are two wayswhere the remote wireless device (RD) controls or communicate withvarious II Devices 140. First, RD is connected to all II Devices in thevicinity and send commands or communicates with one by one in a serialfashion. Second, RD communicates with one or few of the II Devices inthe vicinity and asks connected II Devices to communicate with otherdevices such as by forming a mesh network. In both the cases all IIDevices 140 may not get commands simultaneously or in parallel becauseof which II Devices actions might not look synchronized even for thesame command. More the number of II Devices, more the time required tosend command to each II Device in the vicinity and worse thesynchronization will be. This could be solved with wireless protocolssuch as Bluetooth Low Energy or BLE4.0 which support broadcasting. Withthis technique the Remote Wireless Device will broadcast the commandsand all the II Devices in the vicinity within the range would get thecommands simultaneously and act as per the commands. Referring to FIGS.74 and 75, the Remote Controlling Device (RD) 7400 broadcasts the dataor commands 7502 and all II Devices within the range receive it and actaccordingly at the same time. In broadcast method here, II Devices 140could be only in listening mode and need not send any acknowledgement toany other device or need not connect to any other device including RD7400. With this there is less traffic of the wireless data flowproviding better control over limited bandwidth availability, lesscommunication error and less lost packets of data transmitted. Inaddition, there could be various individual or groups of II Devices thatRD 7400 want to send commands at a time using broadcast method 7502.With broadcast all II Devices within the range receive the data/command7504 from RD. The II Devices would check if the commands are intendedfor them as individually or part of a group 7506. And only those IIDEVICE(s) would act/respond as per the commands to whom the command isintended for 7508, 7510. This is possible by having an identificationnumber such as for individual II DEVICE(s) or group of II DEVICE(s) inthe broadcast commands from RD 7400. In addition, if required the remotedevice with the device application could broadcast at least one commandintended to at least one II Device asking to go into listening mode7512. In listening mode II Device do not broadcast or transmit themessages to other wireless devices reducing the required bandwidthtraffic. This may be required especially if II Devices are broadcastingany information or communicating to other devices causing increase intraffic in the available communication bandwidth. With II Devices goinginto the listening mode, the traffic will reduce helping reliability ofthe message transfer from remote wireless device to II Devices.

The modularity so that one can build his/her own lighting fixture willnow be described. The lighting industry has been dependent on theexisting form factors of lighting devices such as bulb, specificfixture, strip light, panels, etc. which are manufactured by thelighting companies and specified to designers. There is no easy toolwhere form factors of lights can be designed and produced at a unitlevel and can be installed in the infrastructure as required. With thisthere are limitations at the lighting installations level because ofdependencies on the available form factors which also define the lightoutput in terms of beam angle, lumens, color temperature, number ofcolors that can be produced, input socket, size and other dimensions,etc. Access to chose and use various parts of any light system invarious capabilities and forms would give any individual or designer todesign a specific light required for a specific area or room of aninfrastructure. For example, with various forms having differentspecifications of different parts of any light such as input powermodule, optics module, control module, diffuser, lens, types of LEDs,form factors of LEDs such as on strip, on different shape of printedcircuit boards meant for bulb, fixtures, panels, etc. designer would beable to design his own lighting devices as per his requirements. Variousparts of a lighting device with different specifications where each partwith at least one function such as providing input power trough mainsinput, controlling device, etc. could be made compatible to at least oneother part performing different function so that when these parts cometogether they can form different variations of lighting device withpermutations and combinations. Referring to FIG. 76 an example is shownof forming lighting devices from various parts. An input power andcontrol module 7600 when combined with one variation of optics module7602 gives one variation of lighting device 7604. Similarly when onevariation of input power and control module 7600 combined with anothervariation of optics module 7612 gives another variation of lightingdevice 7606. Furthermore, the optic module 7602 could be of differentparts with one diffuser lens 7610 or another diffuser lens 7608 part ofit giving variations in optics module, here in terms of light output.

A software tool can provide a user or designer with all variations ofall parts/modules that can be used to virtually form or design or createmultiple different lighting devices through permutations andcombinations. The user is able to select the various parts/modulesrequired to design the lighting device using the software andpotentially able to test the design for various parameters. Referring toFIG. 77, the user or designer can launch the software 7700 for designingthe lighting device. On the software tool, the user can see variousavailable parts/modules or combinations thereof 7702 which can be chosenand combined with different permutations and combinations 7704 to format least one lighting device. The parts include but not limited to:

-   -   1. Various power modules 7710—Various Power Modules are formed        based on different input voltages, power rating, voltage and        current outputs, form factors, input and output connectors, etc.    -   2. Various control modules 7718—Various Control modules are        formed based on different input voltage and current supplies,        processing/controlling units, various internal or external LED        drivers, internal or external communication modules, form        factors, input and output connectors, etc.    -   3. Various optics modules 7712—Various optics modules are formed        based on different beam angles, color and saturation types, LED,        laser other light emitting device types, form factors, diffuser        types, input and output connectors, etc.    -   4. Various housing modules 7714—Various housing for each part or        combination thereof based on color, material, physical        properties, entire housing in terms of various fixtures, panels,        etc.    -   5. Various modular connectors and cables for connecting parts or        combination(s) thereof 7716—Various connectors and cables for        connecting parts based on length, color, form factors, physical        and electrical properties, etc.        Once the lighting device is designed virtually on the software,        user could test it for at least one parameter 7706 and make        necessary changes in the design. The parameters include but not        limited to light output in terms of luminosity, color and beam        pattern, power requirement, aesthetics, etc.

Now referring to FIG. 78, a block diagram showing a lighting device forgeographical travel, especially from one time zone to the other or spacetravel. The overhead light 7800 on a passenger seat 7804 could be madeintelligent such as II Device 140 which can be programmed to providesimulated cycle of the sunlight throughout the day which could helpreduce the effect of jet lag or other travel fatigue especially when thegeographical locations of travel are far affecting the circadian clockof the user. The user can program the II Device 7800 to provide thesimulated light based on his travel locations and day and times of thetravel. Or user can input the information such as travel destinationsand travel timings so that software controlling the II device calculatesand provide required simulated light output. The II Device here need notbe wireless, but could be wired directly to the controlling orprogramming device 7806 which provides the user interface for providingthe inputs or directly programming the II Device 7800. There arenumerous applications of such system such as in airplanes where userwith simulated lighting could have better sleep pattern and minimize thejet lag effect.

Referring to FIG. 79, a flow chart illustrating how a user might want toprogram at least one II DEVICE 140 to produce light as a function of atleast one variable is shown. The variables are such that when changedcould affect user's daily activities and may include, but are notlimited to:

-   -   1. Geographic location 7920;    -   2. Sunrise time 7910;    -   3. Sunset time 7910;    -   4. Date 7914;    -   5. Time of the day 7914;    -   6. Wake up time (can be provided by alarm software on the        wireless device such as Smartphone) 7918;    -   7. Bed time when user goes to sleep 7916;    -   8. Travel schedule from one geographic location to the other        7912;    -   9. Age of the user 7922;    -   10. Light with warm and cool color temperature light.

There are multiple steps to create such programs for II DEVICE 140.First step involves launching the lighting device software on a wirelessdevice 7900, while in the next step 7902 the device software gathersinformation on at least one type of variables mentioned above eitherfrom the wireless network or user provides the required informationdirectly. Another step 7904 involves user programming at least one IIDEVICE 140 to produce particular light at particular times as a functionof at least one such variable mentioned above. The program(s) can besaved in the internal memory 108 of II DEVICE 140 or external memorysuch as that of wireless device and can be repeated by user as and whenrequired as shown in step 7906.

The user can also program the II DEVICE as a function of at least onevariable mentioned above and at least one variable as below:

-   -   1. Maximum warmness in terms of color temperature, such as light        with 2300K color temperature is considered as a warm light;    -   2. Maximum coolness in terms of color temperature, such as light        with 6000K color temperature is considered as a cool light;    -   3. Sensor input such as that from temperature information from a        temperature sensor in a particular room.

Referring to FIG. 80, the user can define the color temperature of thelight output as a function of time 8002. For example, the user candefine the cool color temperature light output from the morning wake uptime till the afternoon and later on day light color temperature lightoutput till the evening and then warm temperature until the user goes tosleep. The function could be step function as described or could also bedefined to gradually change the color temperature light output from onepoint of time to the other 8004. For example, the cooler temperature tothe warmer temperature change could be with some function such as linearor exponential 8004. In addition with the variables mentioned above theII Device(s) 140 or Device application can learn the behavior of theuser that can be used directly to create program(s) to produce therequired light output at required times. This program can be a defaultprogram and user could customize it with the inputs of various times,color temperature changes at those times and function for gradual changein the color temperature from the one color temperature to the other.The user interface on the wireless device communicating with the IIDevice(s) 140 would provide the ability to the user to provide the time,color temperature and function inputs. The programs created could bestored in the internal memory 108 or external memory such as that of thewireless device 8006. In addition, the programs could be modified ormore programs could be added as and when required through the userinterface on the wireless device 8008.

There could be multiple programs running for at least one II DEVICE 140either internally in II DEVICE 140 itself or in external wirelessdevices such as Smartphone running application for II DEVICE 140. Theseprograms could be function of time with which there may be conflictswhile running various programs. The priority needs to be assigned toensure the important programs override the less important programs forII DEVICE(s) 140. Referring to FIG. 81, this can be achieved by havinguser assign the priority for various programs through the user interfacesoftware running on the wireless device for controlling II DEVICE(s)8104. The priority can be assigned in terms of numerical values or levelsuch as “High”, “Medium”, “Less” 8104. There could be pre-defined ordefault programs with assigned priority which cannot be changed. On theuser interface, the user can see all programs running for single ormultiple II Devices in a list or grid or any other format and can assignthe priority as required 8102. The priority can be stored in theinternal memory of II Device or the external memory such as memorycommunicable coupled to the wireless device communicating with the IIDevice 8106. Different programs can have different priorities as afunction of day or sensor input or any other condition 8104. Forexample, the program of light output in terms of color temperaturechange as a function of time of the day can have higher priority overthe program for light output from II Device as a function of weatherchanges unless the weather condition becomes very harsh crossing thedefined limit and warning has to be given to the user with certain colorlight output from the II Device(s).

FIG. 82 is a block diagram illustrating how a lighting device can beused with fluorescent objects. Black light also known as ultravioletlight can be part of the II Device 140 or 8200 as at least one type ofLED. Black lights are employed for decorative and artistic lightingeffects particularly in observing fluorescence, in which illuminatingcertain materials with UV radiation causes the emission of visiblelight, causing these substances to glow with various colors. The IIDevice 140 or 8200 can have the black light LEDs controlled in a similarfashion as other color LEDs are controlled. However, considering thepotential health hazards of the UV light an important provision can bemade to limit the duration and average current flowing through the blackLED. As shown in FIG. 83, the II Device software could impose the limiton the maximum average current passing through the Black Light LED 8302,by limiting the duty cycle of the PWM signal passing through the BlackLight LED or by limiting the maximum ON time as compared to OFF time ofthe signal for Black Light LED 8302. In addition, the IID also limit theduration of the Black Light LED total duration of the functioning 8304.For example, the duration for which it is functioning could be limitedto 5 minutes in a particular given time interval such as 1 hour. hiscould be achieved by using the internal clock of the processor 106 orreal time clock 110 of the II Device 140. With black LED one user couldprovide artistic lighting effect by illuminating various objects withfluorescence abilities.

Laser diode can be a part of the II Device 140 as at least one type ofLED. Laser diodes are employed for entertainment lighting effects. TheII Device 140 can have the laser diode of one or multiple colors lightoutput controlled in a similar fashion as other color LEDs arecontrolled. However, considering the potential health hazards of thelaser diode output light an important provision can be made to limit theduration and average current flowing through the laser diode. The IIDevice software could impose the limit on the maximum average currentpassing through the Laser Diode 8302, by limiting the duty cycle of thePWM signal passing through the Laser Diode or by limiting the maximum ONtime as compared to OFF time of the signal for Laser Diode 8302. Inaddition, the II Device can also limit the duration of the Laser Diodetotal duration of the functioning 8304. For example, the duration forwhich it is functioning could be limited to 5 minutes in a particulargiven time interval such as 1 hour. This could be achieved by using theinternal clock of the processor 106 or real time clock 110 of the IIDevice 140. With Laser Diode a user could provide entertaining lightingeffect by emitting the laser beams at various places in the room.

Any selection level of a system, level, room, group, or individual IIDevice 140 can be set in combination with a command (configuration,program, or effect) to execute at a designated future time asrepresented in FIG. 84. Similar to a program, here an extension ofprogram is to interpret that a user can schedule any number of IIDevices 140 to do certain things at different times outlined in flowchart 8400. Including but not necessarily in this order, the schedulingprogram (8402) a user would select any combination of II Devices (8404).Then a user would select an automation or time characteristic (8406),including but not limited to time start/end, day start/end, day of theweek start/end, or duration. The schedule could then be set to haveadditional properties (8408) such as repeatability (repeating on someschedule), effect commands such as fade-in or fade-out commands, or thelike. Also, the user may specify the light command associated with theschedule select a pre-defined light command (8410). One II Device canhave multiple future schedules. Similarly any selection level, such as aroom, can have multiple schedules.

The selected schedule may then be stored in the related II Devices(8412), within the user interface (8414), or stored in an outsidenetwork like cloud storage (8416). At the appropriate scheduledcondition, the II Devices in coordination with the related components ofthe lighting network would execute the set command in accordance withthe additional properties (8418). The schedule may be presented to theuser in a variety of ways (a user can see the set future scheduledevents for any selection level of II Devices. These scheduled eventscould be organized and sorted based on the soonest to occur showingfirst. In addition, the scheduled events could have representations onwhat the command is, including color, brightness, program, effect or thelike. Moreover, the II Device could show inherited schedules from higherlevels of hierarchy, such that a single II Device could show a scheduleset for a group that it is associated with. Furthermore, the schedulecould be associated to a user.

Referring to FIG. 85, an option could be made in the user interface toenact an eco mode for any level of control (8500). The eco mode would begeared towards optimizing efficiency with regards to energy usage. Forexample, the selected lights would be dimmer using less energy. Inaddition, other applications like proximity, sunset/sunrise monitoring,ambient light sensing, and other information could be used to create aneco footprint.

For example, when a user selects the eco mode option, it can set areduced energy usage (8502) for the related II Devices that would belower than the overall maximum energy usage (8503). The lowered energyusage here could be attributed and associated with a reduction in lightoutput, wireless strength, or light qualities such as CRI or colortemperature. In addition, the lowered maximum energy usage might bevariable over time (8504) with respect to the general maximum energyusage (8503). This variable energy usage (8504) could be related to anadditional condition such as time of day, seasonality, availablesunlight, as a proportion of the general energy usage, or with respectto other conditions (8506). For example, the Eco mode might be triggeredor controlled with respect to overall power grid demand. Here, a signalcould be sent to the WD or directly to the II Devices indicating ahigh-demand period of energy use as a condition (8506). In response avariable eco-mode maximum energy usage could be set (8504) so that thepower consumption of the II Devices is reduced. The Eco mode could be ageneral selection mode on top of any other command limiting the overallbrightness produced by the II Devices. Or, the eco mode could be limitedto a set number of II Devices and any other configuration would be inreplacement to the Eco configuration.

As shown in FIG. 86 in a monitoring program (8600), each II Device orthe controlling device has the ability to monitor when and for how longand at what setting the related II Device is active or inactive (8602),and the II Device can associate that with an approximate energy usagerequired (8604) and relay that information back to the controllingdevice. The controlling device can then summarize and display thatinformation in a user interface screen (8606) to summarize the energyusage of one or many II Devices. The energy usage might be translated toalternative metrics such as $'s or carbon dioxide offset. Thisinformation could be tracked under multiple parameters such as YTD, pastweek, lifetime, and the like. This information could be stored locallyin the app, saved to an associated cloud location, or sent to analternate source such as a utility monitoring program or the like.

As the connected device has access to the web either through a localarea network or a wireless network, the application could access variousdata feeds via the connected device on the web that can be used asprogramming inputs to one or more II Devices as referenced in FIG. 87(8700). The data feed (8701) would be accessed by the IID or connecteddevice (8702). Alternatively, there could be a bridge or secondaryconnected device within the lighting network that is connected to theweb and has access to the web service data feeds (8703). The data wouldthen be mapped and interpreted into one or more light settings for theone or more IIDs (8704). The mapping and interpretation could be througha combination of predefined or user defined methods.

The data feeds could be accessed with one or more data access settings(8706) including but not limited to a one-time access, continuouslyaccessed, accessed upon a condition or event, or upon user input.Example conditions for the data programming could be defined from a timeof day, calendar day, day of week, additional data condition, additionalprogram, or any combination thereof. For example, various local weatherdata feeds could be accessed through various web services on theconnected device. This information could then be used to createdifferent lighting configurations or settings, such as a light beingbluer or redder based on the temperature. In addition, the weatherinformation could be used to assume the overall overcast conditions andlevel of brightness and similarly adjust any number of II Devicesaccordingly.

A user could schedule the data programming functions for a set time orreoccurring dates/times associated to any number of II Devices. Forexample, a user could set a weather program to have an II Device toreflect the weather outside on weekdays from 7 am to 8 am. Only at thattime would the II Device and the controlling devices look for the datainformation, send it to the associated II Device and the associatedcommand.

Other forms of data include but are not limited to, stock or commoditytrading or market information, incoming phone calls or messages,application or web alerts such as those from social media applications,sunset/sunrise times, or any other data feed indicators.

There can be a program as shown in FIG. 88 where the application devicecan be set to record a series of actions executed by the II Devices andplayed back at a later time (8800). Initially, a setting would beselected within the controlling device to begin the recording (8802).The controlling device and/or II Devices would then monitor anyinteraction and/or actions taken by one or more II Devices (8804). Theuser's interaction and actions could come from an outside program orthrough direct user interaction through the controlling device to one ormany II Devices over a time period. The intended one or more series ofinteractions and actions can then be recorded and committed to memory(8806). Afterwards the recording of the sequence of one or more commandscan be replayed upon a user request or through some other program(8808). This would allow someone to set-up favorite effect or programsequences and recall the sequence of settings at any time. The sequencecould be a function of a general step-by-step sequence or it may be afunction of time between each step of the sequence. A user could havethe ability after recording to edit the recording in various ways(8810), cropping, cutting, adjusting the time, or changing any number ofdifferent aspects of the recorded lighting sequence as required.

Within the device application a user can create or have access topredefined lighting effects. These effects can simulate certainenvironments, ambiances, or functional aspects. A user can select aneffect, select any number of II Devices (either through groups/rooms, orindividual control), then execute that effect at that time or upon afurther schedule. These effects range from simulating certainenvironments, such as a moving blue ocean, flickering orangecandlelight, a strobe, or other effects, to other lighting effectsbeneficial for film or general use such as, fire, television, lightning,headlights, flashes of light from explosions/gun fire. Further, theeffect might be linked to some other event such as taking a photo andhaving a flash effect.

A photo or video is composed of a series of pixels that have anassociated color. In this sense, these pixels can be extracted to relateto a command given to one or many II Devices in an image reflectionprogram as referenced in FIG. 89 (8900). The associated commands couldbe similar all relating to a general type of pixel or each differentwith different selected pixels associated to different II Devices. Fromphoto or video (8901), an image including content and informationrelating to color elements or pixels within that photo or video will beobtained either through the controlling device, the applicationinterface, a display signal, or an outside means (8902). The image andassociated color element could be broken out into one or more differentareas of the picture (8904). Additionally, the image could becompressed, converted, or modified as needed. This break-up could bedone based on contrasting dominant color schemes, x & y coordinates orquadrants within the image, a user selection, a random sampling of theimage, or some combination of the previous. These various broken outareas can then be interpreted either via an average, modal, or otherapproach into one or more colors (8906). These colors can then be mappedto one or more II Devices (8908). In addition, the assignment of pixelsto one or many II Devices can be user generated or automated. Ifautomated, the device application could use information on the layout ofthe II Devices in the proximity location to help identify spatialrelationships where the II Devices are related to a frame. The relatedII Devices would then emit a light associated with the interpretedcolors (8910).

A sequence of pictures or video could similarly be monitored as asequence of images or frames over time (8912). This could be done basedon every frame or a defined number of frames to optimize theperformance. The photo or video could be viewed directly on theconnected device or a separate display, such as a television. If in aseparate display, the connected device could be an intermediary betweenthe display and the II Devices. Alternatively, the display can bedirectly connected to the II Devices or have a connected router orbridge that can monitor the display and send a command directly to theII Devices. The overall effect would provide a light setting or sequencethat extends the visual display of an image to the ambient environment.This would immerse a user within an image or video and create thepotential for a surround effect with lighting.

Referring to FIG. 90, a process for creating a scene in a quick andconvenient fashion is described (9000). Through general use, a user willgo through the effort of personalizing and creating a combination oflight settings in relation to one or more II Devices, or scenes. Itwould therefore be convenient to the user to easily save and replaythese scenes without going through the process of returning eachindividual II Device. Instead, the wireless device working with thedevice application can at any time capture the scene as the currentstate of the one or more II Devices and their respective light setting(9002). The capture can either be through a manual user interaction withthe device application (9003) or upon some other event such as throughan automated timeframe or as part of a program (9004). Additionally, thecapture of the scene could be taken from a static lighting setting or asa single frame from within a dynamic light setting. The one or more IIDevices could be captured in an individual or a group form.

After capturing the scene, the one or more II Devices and their relatedlight settings could be saved to the device or application memory as anew scene (9005). The process of saving could be automatic or requiremanual input or interaction to save. The saved new scene could then beviewed or edited (9006) to adjust any metadata or settings related tothe one or more II Devices and their related light settings. The scenecould also be replayed or executed at a later time either through a userinteraction within the device application or through some user orpre-defined program (9008). At which point, the one or more II Deviceswill then emit the saved light settings as originally captured andstored within the scene (9010).

As lighting is fairly well and universally distributed, the function ofthe II Devices 140 might be used to provide various location servicesand interactions as represented in FIG. 91. Here, one or more II Devices140 could be placed in an area (9102). The II Devices defined at aminimum of requiring a wireless transceiver/receiver and one or moreLEDs. The II Devices would be set to send out a periodic message thatincludes an identifier for each specific II Device (9104). Theidentifier could be user defined or predefined. Similarly, the IIDevices could monitor or listen for the presence of other wirelesslyaddressable devices within range (9106), as example if the II Deviceuses Bluetooth then the II Device 140 would look for all availableBluetooth devices within range. Also, the II Devices could alternatebetween a sending and listening mode (9108).

The II Device could then find one or more compatible wirelesslyaddressable device within range or the wirelessly addressable devicecould find one or more II Devices within range (9110). After the one ormore II Devices and the one or more wirelessly addressable devices findeach other, a predefined or user defined action may result (9112). Oneexample action includes prompting the wirelessly addressable device witha message or advertisement (9114). Another example action includesmatching the II Device identifier with some other information storedwithin the wirelessly addressable device or a related device application(9116). Here, the II Device identifier could be associated to a specificlocation key within the space. Another example action includes thewirelessly addressable device sending a command to the one or more IIDevice to change to a different light setting (9118). At the same time,a sequence within a device application on the wirelessly addressabledevice could be triggered that changes the view of the deviceapplication to bring up location specific content (9120). Similarly, theone or more II Devices could change to draw attention to that space,perhaps changing color, brightness, or executing a lighting effect.

There might also be a sequence of actions taken as a combination orresult of any of the predefined actions between the one or more IIDevices and the wirelessly addressable devices (9122). As example, aftera first action between an II Device and the wirelessly addressabledevice where the II Device identifier is recorded by the wirelesslyaddressable device, the wirelessly addressable device could send amessage through the web to a separate database that records theinteraction taking place along with other metadata including the time ofthe interaction, the length of the interaction, the signal strength ofthe interaction, or other information.

It will be understood by those of skill in the art that information andsignals may be represented using any of a variety of differenttechnologies and techniques (e.g., data, instructions, commands,information, signals, bits, symbols, and chips may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof). Likewise, thevarious illustrative logical blocks, modules, circuits, and algorithmsteps described herein may be implemented as electronic hardware,computer software, or combinations of both, depending on the applicationand functionality. Moreover, the various logical blocks, modules, andcircuits described herein may be implemented or performed with a generalpurpose processor (e.g., microprocessor, conventional processor,controller, microcontroller, state machine or combination of computingdevices), a digital signal processor (“DSP”), an application specificintegrated circuit (“ASIC”), a field programmable gate array (“FPGA”) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. Similarly, steps of a method orprocess described herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Althoughpreferred embodiments of the present invention have been described indetail, it will be understood by those skilled in the art that variousmodifications can be made therein without departing from the spirit andscope of the invention as set forth in the appended claims.

What is claimed is:
 1. A lighting device comprising: an AC/DC or DC/DCpower converter; a controller/processor electrically connected to theAC/DC or DC/DC power converter; a light emitting diode (LED) currentcontrol circuit communicably coupled to the controller/processor andelectrically connected to the AC/DC or DC/DC power converter; and one ormore LEDs electrically connected to the LED current control circuit. 2.The lighting device as recited in claim 1, wherein the one or more LEDscomprise at least a first type or color LED and a second type or colorLED.
 3. The lighting device as recited in claim 1, further comprising ahousing having a bi-pin connector, wherein the AC/DC or DC/DC powerconverter, the controller/processor and the LED current control circuitare disposed within the housing, and the bi-pin connector iselectrically connected to the AC/DC or DC/DC power converter.
 4. Thelighting device as recited in claim 1, further comprising a housinghaving a plug-in connector, wherein the AC/DC or DC/DC power converter,the controller/processor and the LED current control circuit aredisposed within the housing, and the plug-in connector is electricallyconnected to the AC/DC or DC/DC power converter.
 5. The lighting deviceas recited in claim 1, further comprising a housing having a batteryconnector, wherein the AC/DC or DC/DC power converter, thecontroller/processor and the LED current control circuit are disposedwithin the housing, and the battery connector is electrically connectedto the AC/DC or DC/DC power converter.
 6. The lighting device as recitedin claim 1, further comprising: a panel housing, wherein the AC/DC orDC/DC power converter, the controller/processor and the LED currentcontrol circuit are disposed within the panel housing; a wire, a cableor a connecting strip electrically connected to the AC/DC or DC/DC powerconverter; an electrical connector electrically connected to the wire,the cable or the connecting strip; and wherein the one or more LEDs areaffixed to the panel housing and electrically connected to theelectrical connector.
 7. The lighting device as recited in claim 1,further comprising: a can light housing wherein the AC/DC or DC/DC powerconverter, the controller/processor and the LED current control circuitare disposed within the can light housing, and the one or more LEDs areproximate to or within an aperture of the can light housing; a wire, acable or a connecting strip electrically connected to the AC/DC or DC/DCpower converter; an electrical connector electrically connected to thewire, the cable or the connecting strip; and a heat sink disposed withinor integrated into the can light housing.
 8. The lighting device asrecited in claim 1, further comprising: a strip wherein the one or moreLEDs are affixed to the strip and electrically connected to theelectrical connector; a first electrical connector affixed to the stripand electrically connected to the two or more LEDs; and the DC/DC powerconverter, the controller/processor and the LED current control circuitare remotely located with respect to the strip and electricallyconnected to the electrical connector via a wire, a cable or aconnecting strip
 9. The lighting device as recited in claim 6, furthercomprising a second electrical connector affixed to the strip andelectrically connected to at least the first electrical connector andone or more other lighting devices.
 10. The lighting device as recitedin claim 1, the one or more LEDs comprising two or more LEDs havingdifferent type or colors, and the LED current control circuit providesan on/off signal having a cycle time to each LED in response to one ormore control signals received from the controller/processor such thattwo or more LEDs produce a blended light having a specified color basedon how long each LED is turned ON and/or OFF during the cycle time 11.The lighting device as recited in claim 10, wherein the specified coloris produced by turning ON the first color LED for a first portion of thecycle time and turning ON the second color LED for a second portion ofthe cycle time.
 12. The lighting device as recited in claim 1, the oneor more LEDs comprising two or more LEDs having different colors and thetwo or more LEDs are not turned ON at the same time.
 13. The lightingdevice as recited in claim 1, the one or more LEDs comprising two ormore LEDs having different colors and each LED is turned ON and OFF fora time period calculated using a count corresponding to a color andbrightness combination.
 14. The lighting device as recited in claim 1,wherein the LED comprises a series of LEDs, a group of LEDs, an array ofLEDs, two or more series-connected LEDs, two or more parallel-connectedLEDs or a combination thereof.
 15. The lighting device as recited inclaim 1, wherein the one or more LEDs comprise a blacklight orultraviolet LED selected to illuminate one or more fluorescent objects.16. The lighting device as recited in claim 1, wherein the one or moreLEDs comprise a laser diode selected to illuminate one or more objectsbased a current or timing limitation of the laser diode.
 17. Thelighting device as recited in claim 1, further comprising a memorycommunicably coupled to or integrated into the controller/processor. 18.The lighting device as recited in claim 1, wherein the LED currentcontrol circuit comprises a PWM driver, a switching or multiplexercircuit, or one or more LED driver circuit.
 19. The lighting device asrecited in claim 1, further comprising an ambient light sensor circuitcommunicably coupled to the controller/processor.
 20. The lightingdevice as recited in claim 19, the ambient light sensor detects a levelof one or more color components of an ambient light, wherein the one ormore color components comprise a red, a green, a blue, a cyan, a yellow,a magenta, or a black.
 21. The lighting device as recited in claim 19,the ambient light sensor is located to detect an ambient light and alight emitted by the lighting device such that the controller/processoradjusts one or more of the on/off signals provided to the two or moreLEDs.
 22. The lighting device as recited in claim 19, wherein theambient light sensor is disposed on a LED board with the one or moreLEDs.
 23. The lighting device as recited in claim 1, further comprisinga hard reset circuit communicably coupled to the controller/processor.24. The lighting device as recited in claim 1, the AC or DC powerconverter comprising a battery, a battery backup or a rechargeablebattery.
 25. The lighting device as recited in claim 1, furthercomprising a wireless energy receiver connected to the DC/DC or AC/DCpower converter.
 26. The lighting device as recited in claim 1, furthercomprising an external switch communicably coupled to thecontroller/processor that controls the lighting device based a programtriggered by a specified number of ON/OFF combinations from the externalswitch within a specified period of time.
 27. The lighting device asrecited in claim 1, further comprising: a wireless transceiver circuitcommunicably coupled to the controller/processor; and an antennacommunicably coupled to the wireless transceiver circuit.
 28. Thelighting device as recited in claim 27, the antenna is external to thelighting device.
 29. The lighting device as recited in claim 27, furthercomprising a signal booster or repeater communicably coupled to theantenna.
 30. The lighting device as recited in claim 27, furthercomprising one or more other lighting devices, remote controllers,wireless controllers, wireless devices, sensors, other devices, or acombination thereof that communicates with the controller/processor ofthe lighting device using the wireless transceiver circuit, the antennaand one or more communication protocols.
 31. The lighting device asrecited in claim 30, further comprising a group of lighting devicescomprising the lighting device and at least two or more of the otherlighting devices.
 32. The lighting device as recited in claim 30,wherein one or more parameters of the lighting device or the one or moreother lighting devices are displayed on the remote controller, wirelesscontroller or wireless device.
 33. The lighting device as recited inclaim 30, wherein the lighting device or the one or more lightingdevices are displayed on the remote controller, wireless controller orwireless device in accordance with a user-defined filter or auser-defined sorting based on one or more criteria.
 34. The lightingdevice as recited in claim 30, the one or more communication protocolscomprising multiple simultaneous communication protocols.
 35. Thelighting device as recited in claim 30, wherein a communication ordiscovery of the one or more other lighting devices, remote controllers,sensors, other devices, or a combination thereof are based on a signalstrength.
 36. The lighting device as recited in claim 30, thecontroller/processor controls the one or more LEDs based on datareceived from the one or more sensors.
 37. The lighting device asrecited in claim 36, further comprising an intermediate devicecommunicably coupled between the controller/processor and the one ormore sensors.
 38. The lighting device as recited in claim 30, whereinthe one or more sensors comprise a motion or accelerometer sensor. 39.The lighting device as recited in claim 30, the controller/processorreceives and executes one or more commands from the one or more otherlighting devices, remote controllers, sensors, other devices, or acombination thereof.
 40. The lighting device as recited in claim 39, theone or more commands comprise one or more voice commands
 41. Thelighting device as recited in claim 39, the one or more commandscomprise one or more broadcast commands.
 42. The lighting device asrecited in claim 39, wherein the one or more commands select and controlone or more groups of lighting devices using a user interface on thewireless controller or wireless device.
 43. The lighting device asrecited in claim 39, wherein the one or more commands select and controlone or more favorites of lighting devices or one or more screens oflighting devices using a user interface on the wireless controller orwireless device.
 44. The lighting device as recited in claim 39, whereinthe one or more commands select and control one or more modes orprograms of lighting devices using a user interface on the wirelesscontroller or wireless device.
 45. The lighting device as recited inclaim 39, wherein the one or more commands select and control a color, abrightness or a saturation of one or more groups of lighting devicesusing a user interface on the wireless controller or wireless device.46. The lighting device as recited in claim 39, wherein the one or morecommands select and control a color, a brightness or a saturation of oneor more favorites of lighting devices using a user interface on thewireless controller or wireless device.
 47. The lighting device asrecited in claim 30, wherein the lighting device and the other lightingdevices are part of a mesh network, a group or a combination thereof.48. The lighting device as recited in claim 47, wherein thecontroller/processor provides a status information to the other lightingdevices, remote controllers or other devices within the mesh network orgroup.
 49. The lighting device as recited in claim 47, wherein thecontroller/processor receives a status information from the otherlighting devices, remote controllers or other devices within the meshnetwork and uses the status information as an input to execute one ormore commands, change the on/off signals, trigger a communication orcommand to the mesh network or group, or a combination thereof.
 50. Thelighting device as recited in claim 47, wherein the controller/processorenters a discovery mode to detect the other lighting devices within themesh network or group when the lighting device is turned on.
 51. Thelighting device as recited in claim 30, wherein the one or more otherdevices relay and/or transmit one or more commands.
 52. The lightingdevice as recited in claim 52, the one or more other devices comprisingan access point, a repeater or a booster.
 53. The lighting device asrecited in claim 1, wherein the controller/processor executes one ormore modes or programs to control the LED current control circuit toproduce a light in accordance with the one or more modes or programs.54. The lighting device as recited in claim 53, wherein the one or moremodes or programs comprise one or more default modes or programs, one ormore user created modes or programs, one or more user profiles, anapplication programming interface program, a diagnostic/testing program,a user interface, or a combination thereof.
 55. The lighting device asrecited in claim 54, wherein the application programming interfaceprogram include a memory read/write function, a sensor communicationsetup function, a color adjustment function, a brightness adjustmentfunction, an amplitude/saturation function communications setupfunction, or a combination thereof.
 56. The lighting device as recitedin claim 54, wherein the one or more user profiles are shared betweenthe lighting device and the one or more other lighting devices.
 57. Thelighting device as recited in claim 53, wherein the one or more modes orprograms include a reintegration mode that when executed reconnects thelighting device to the one or more other lighting devices.
 58. Thelighting device as recited in claim 53, wherein the one or more modes orprograms when executed selects a level of control of the lightingdevice, converts the selected level of control into one or more lightcontrol settings, and transmits the one or more light control settingsto the lighting device for execution by the controller/processor. 59.The lighting device as recited in claim 53, wherein the one or moremodes or programs when executed selects the lighting device or one ormore other lighting devices, and assigns the selected lighting device(s)to a new or existing group of lighting devices.
 60. The lighting deviceas recited in claim 53, wherein the one or more modes or programs whenexecuted selects the lighting device, one or more other lighting devicesor one or more groups of lighting devices, selects a configuration orone or more settings for the selected lighting device(s), selects atiming condition when the selected configuration or settings are toexecuted, and saves the selected timing condition and selectedconfigurations or settings as an automated mode or program.
 61. Thelighting device as recited in claim 53, wherein the one or more modes orprograms includes a soft reset process.
 62. The lighting device asrecited in claim 53, wherein the one or more modes or programs includesa visual or virtual representation of the lighting device located withinone or more spaces.
 63. The lighting device as recited in claim 53,wherein the controller/processor includes a security program that whenexecuted prevents unauthorized access to the one or more modes orprograms.
 64. The lighting device as recited in claim 53, wherein atleast one of the one or more modes or programs are assigned a priority.65. The lighting device as recited in claim 53, wherein the one or moremodes or programs comprise a learning program that when executed learnsan activity, routine or behavior of a user and operates the lightingdevice in accordance with the activity, routine or behavior of the user.66. The lighting device as recited in claim 53, wherein the one or moremodes or programs comprise a circadian clock program.
 67. The lightingdevice as recited in claim 53, wherein the one or more modes or programswhen executed adjust the lighting device as a function of a colortemperature and a time.
 68. The lighting device as recited in claim 53,wherein the one or more modes or programs comprise a scheduling program.69. The lighting device as recited in claim 53, wherein the one or moremodes or programs comprise an energy reduction program, energymonitoring program, energy reporting program, or a combination thereof.70. The lighting device as recited in claim 53, wherein the one or moremodes or programs comprise a data program that when executed translatesa data feed into one or more light settings or commands based on one ormore user-defined or default settings.
 71. The lighting device asrecited in claim 53, wherein the one or more modes or programs comprisea recording program that when executed captures and plays back one ormore commands received by the lighting device.
 72. The lighting deviceas recited in claim 53, wherein the one or more modes or programscomprise an image reflection program that when executed translates oneor more images, sequences of images or characteristics of images intoone or more lighting conditions.
 73. The lighting device as recited inclaim 53, wherein the one or more modes or programs comprise a quickscene creation program that when executed captures, saves and executesone or more scenes or settings.
 74. The lighting device as recited inclaim 53, wherein the one or more modes or programs comprise a locationservices and interactions program.
 75. The lighting device as recited inclaim 1, the controller/processor includes a mode or program that whenexecuted provides two or more layers of control over the lightingdevice.
 76. The lighting device as recited in claim 1, furthercomprising a housing wherein the AC/DC or DC/DC power converter, thecontroller/processor and the LED current control circuit are disposedwithin the housing, and the one or more LEDs are proximate to or withinan aperture of the housing.
 77. The lighting device as recited in claim76, further comprising a heat sink disposed within or outside thehousing.
 78. The lighting device as recited in claim 76, furthercomprising a reflector disposed within the aperture of the housing andaround the two or more LEDs.
 79. The lighting device as recited in claim76, further comprising a diffuser or lens sealing the aperture of thehousing.
 80. The lighting device as recited in claim 1, furthercomprising a control connector, a programming connector or a diagnosticsconnector communicably connected to the controller/processor.
 81. Thelighting device as recited in claim 1, wherein the AC/DC or DC/DC powerconverter, the controller/processor, the light emitting diode (LED)current control circuit and the one or more LEDs are configured into twoor more modules.
 82. The lighting device as recited in claim 81, furthercomprising a program for virtually designing the lighting device using aset of modules selected from the two or more modules and a set ofparameters.
 83. The lighting device as recited in claim 82, the programfurther comprising testing one or more parameters of the virtuallighting device.
 84. A lighting system comprising: two or lightingdevices, wherein each lighting device comprises: an AC/DC or DC/DC powerconverter, a controller/processor electrically connected to the AC/DC orDC/DC power converter, a light emitting diode (LED) current controlcircuit communicably coupled to the controller/processor andelectrically connected to the AC/DC or DC/DC power converter, one ormore LEDs electrically connected to the LED current control circuit, awireless transceiver circuit communicably coupled to thecontroller/processor, and an antenna communicably coupled to thewireless transceiver circuit; and wherein the controller/processors ofthe two or more lighting devices communicate with one another using thewireless transceivers and antennas of the two or more lighting devices.85. A method for controlling one or more lighting devices comprising thesteps of: providing the one or lighting devices, wherein each lightingdevice comprises: an AC/DC or DC/DC power converter, acontroller/processor electrically connected to the AC/DC or DC/DC powerconverter, a light emitting diode (LED) current control circuitcommunicably coupled to the controller/processor and electricallyconnected to the AC/DC or DC/DC power converter, and one or more LEDselectrically connected to the LED current control circuit; sending oneor more control signals from the controller/processor to the LED currentcontrol circuit corresponding to a blended light having a specifiedcolor; and sending an on/off signal having a cycle time from the LEDcurrent control circuit to each LED in response to the one or morecontrol signals such that the two or more LEDs produce the blended lighthaving the specified color based on how long each LED is turned ONand/or OFF during the cycle time.